Percona Server moved to https://jira.percona.com/projects/PS

Merge lp:~hrvojem/percona-server/bug792351-5.5 into lp:percona-server/5.5

  1. bug792351-5.5
  2. Merge into 5.5
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: no longer in the source branch.
Merged at revision: 269
Proposed branch: lp:~hrvojem/percona-server/bug792351-5.5
Merge into: lp:percona-server/5.5
Diff against target: 203 lines (+42/-31)
9 files modified
doc/source/diagnostics/innodb_stats.rst (+1/-4)
doc/source/diagnostics/slow_extended_55.rst (+2/-3)
doc/source/flexibility/buff_read_ahead_area.rst (+1/-1)
doc/source/management/innodb_expand_import.rst (+1/-1)
doc/source/management/udf_maatkit.rst (+16/-17)
doc/source/reliability/innodb_recovery_update_relay_log.rst (+2/-2)
doc/source/scalability/innodb_expand_undo_slots.rst (+2/-2)
doc/source/scalability/innodb_io_55.rst (+14/-1)
doc/source/upgrading_guide_51_55.rst (+3/-0)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug792351-5.5
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+111193@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/diagnostics/innodb_stats.rst'
2--- doc/source/diagnostics/innodb_stats.rst 2012-01-09 04:24:39 +0000
3+++ doc/source/diagnostics/innodb_stats.rst 2012-06-20 11:16:22 +0000
4@@ -58,10 +58,7 @@
5 :default: 0
6
7
8-If this option is enabled, |XtraDB| uses the ``SYS_STATS`` system table to store statistics of table indexes. Also, when |InnoDB| opens a table for the first time, it loads the statistics from ``SYS_STATS`` instead of sampling index pages. If you use a high ``stats_sample_pages`` value, the first open of a table is expensive. In such a case, this option will help. Note: This option may cause less frequent updating of statistics. So, you should intentionally use the ``ANALYZE TABLE`` command more often.
9-
10-(This variable was introduced in release 5.1.50-11.4.)
11-
12+If this option is enabled, |XtraDB| uses the ``SYS_STATS`` system table to store statistics of table indexes. Also, when |InnoDB| opens a table for the first time, it loads the statistics from ``SYS_STATS`` instead of sampling index pages. If you use a high ``stats_sample_pages`` value, the first open of a table is expensive. In such a case, this option will help. Intended behavior is to never update statistics unless an explicit ``ANALYZE TABLE`` is issued.
13
14 INFORMATION_SCHEMA Tables
15 =========================
16
17=== modified file 'doc/source/diagnostics/slow_extended_55.rst'
18--- doc/source/diagnostics/slow_extended_55.rst 2012-02-24 09:51:35 +0000
19+++ doc/source/diagnostics/slow_extended_55.rst 2012-06-20 11:16:22 +0000
20@@ -8,7 +8,7 @@
21
22 The ability to log queries with microsecond precision is essential for measuring the work the |MySQL| server performs. The standard slow query log in |MySQL| 5.0 has only 1-second granularity, which is too coarse for all but the slowest queries. |MySQL| 5.1 has microsecond resolution, but does not have the extra information about query execution that is included in the |Percona Server|.
23
24-You can use Maatkit``s mk-query-digest tool to aggregate similar queries together and report on those that consume the most execution time.
25+You can use Percona-Toolkit's pt-query-digest tool to aggregate similar queries together and report on those that consume the most execution time.
26
27
28 Version Specific Information
29@@ -175,7 +175,6 @@
30
31 The option accepts fractional values. If set to 0.5, for example, queries longer than 1/2 second will be logged.
32
33-If the value is set to 0, then all queries are logged. This is different from the standard |MySQL| build, where a value of 0 disables logging.
34 Before version 1.01 of this feature, the value was an integer, and the unit of time was microseconds, not seconds.
35
36 .. variable:: slow_query_log_timestamp_always
37@@ -370,7 +369,7 @@
38 Related Reading
39 ===============
40
41- * http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/
42+ * `Impact of logging on MySQL's performance <http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/>`_
43
44 * `log_slow_filter Usage <http://www.mysqlperformanceblog.com/2008/09/22/finding-what-created_tmp_disk_tables-with-log_slow_filter/>`_
45
46
47=== modified file 'doc/source/flexibility/buff_read_ahead_area.rst'
48--- doc/source/flexibility/buff_read_ahead_area.rst 2012-02-13 08:49:21 +0000
49+++ doc/source/flexibility/buff_read_ahead_area.rst 2012-06-20 11:16:22 +0000
50@@ -33,4 +33,4 @@
51 Other Reading
52 =============
53
54- * `BUF_READ_AHEAD_AREA Bottleneck <http://www.facebook.com/notes/|MySQL|facebook/using-pmp-to-double-|MySQL|-throughput-part-2/405092575932>`_
55+ * `BUF_READ_AHEAD_AREA Bottleneck <http://www.facebook.com/notes/mysqlfacebook/using-pmp-to-double-mysql-throughput-part-2/405092575932>`_
56
57=== modified file 'doc/source/management/innodb_expand_import.rst'
58--- doc/source/management/innodb_expand_import.rst 2012-06-04 13:39:55 +0000
59+++ doc/source/management/innodb_expand_import.rst 2012-06-20 11:16:22 +0000
60@@ -131,7 +131,7 @@
61 .. lock all tables in the database ``example``
62 .. "ALTER TABLE ... DISCARD TABLESPACE" for all tables in ``exmple``
63 .. unlock all tables in the database ``example``
64-.. (and we need to get all create table clause (e.g. "|MySQL|dump --no-data"))
65+.. (and we need to get all create table clause (e.g. "mysqldump --no-data"))
66 .. obtain *.ibd *.exp as exported files
67 .. Target: (innodb_expand_import should be 1)
68
69
70=== modified file 'doc/source/management/udf_maatkit.rst'
71--- doc/source/management/udf_maatkit.rst 2011-10-07 23:38:41 +0000
72+++ doc/source/management/udf_maatkit.rst 2012-06-20 11:16:22 +0000
73@@ -6,17 +6,19 @@
74
75 Three *Percona Toolkit* and *Maatkit* UDFs that provide faster checksums are provided:
76
77- * ``fnv_udf``
78-
79- * ``fnv1a_udf``
80-
81- * ``murmur_udf``
82+ * ``libfnv_udf``
83+
84+ * ``libfnv1a_udf``
85+
86+ * ``libmurmur_udf``
87+
88+Tools that do checksumming of data (pt-table-checksum, pt-table-sync) will use these functions if they are installed. These are much faster and have better data distribution than CRC32() or MD5() or similar, which are the default functions built into |MySQL|.
89
90 Version Specific Information
91 ============================
92
93- * 5.1.53-12.4:
94- Began distributing ``fnv_udf``, ``fnv1a_udf``, and ``murmur_udf``.
95+ * 5.5.8-20.0:
96+ Began distributing ``libfnv_udf``, ``libfnv1a_udf``, and ``libmurmur_udf``.
97
98 Other Information
99 =================
100@@ -27,20 +29,17 @@
101 Installation
102 ============
103
104-Use of the Percona Software Repositories simplifies the installation of *Percona Toolkit*. Once the repository has been set up on your system, *Percona Toolkit* can be installed by executing: ::
105-
106- $ yum install percona-toolkit
107-
108-This will place the *Percona Toolkit* UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF``s into the server, execute one of the following commands, depending on which UDF you want to install: ::
109-
110- $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME ``fnv_udf.so``"
111- $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME ``fnv1a_udf.so``"
112- $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME ``murmur_udf.so``"
113+These functions are distributed with the |Percona Server| installation. Installing the |Percona Server| will place the UDFs onto your system. However, they will not yet be installed into the |MySQL| server. To install one of the UDF's into the server, execute one of the following commands, depending on which UDF you want to install: ::
114+
115+ $ mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
116+ $ mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
117+ $ mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
118
119 Executing each of these commands will install its respective UDF into the server.
120
121-If you have any difficulty, or require more detailed information, refer to the *Maatkit* `Installing UDFs <http://code.google.com/p/maatkit/wiki/InstallingUdfs>`_ documentation.
122+Confirm that the installation succeeded by running a command such as ::
123
124+ mysql> SELECT fnv_64('hello world');
125
126 Other Reading
127 =============
128
129=== modified file 'doc/source/reliability/innodb_recovery_update_relay_log.rst'
130--- doc/source/reliability/innodb_recovery_update_relay_log.rst 2012-02-16 10:24:41 +0000
131+++ doc/source/reliability/innodb_recovery_update_relay_log.rst 2012-06-20 11:16:22 +0000
132@@ -99,6 +99,6 @@
133
134 * Another solution for |MySQL| 5.0 is `Google's transactional replication feature <http://code.google.com/p/google-mysql-tools/wiki/TransactionalReplication>`_, but it had some problems and bugs.
135
136- * `Related bug (fixed and re-implemented in this feature) <http://bugs.|MySQL|.com/bug.php?id=34058>`_
137+ * `Related bug (fixed and re-implemented in this feature) <http://bugs.mysql.com/bug.php?id=34058>`_
138
139- * `A blog post explaining how this feature makes replication more reliable <http://www.|MySQL|performanceblog.com/2009/03/04/making-replication-a-bit-more-reliable/>`_
140+ * `A blog post explaining how this feature makes replication more reliable <http://www.mysqlperformanceblog.com/2009/03/04/making-replication-a-bit-more-reliable/>`_
141
142=== modified file 'doc/source/scalability/innodb_expand_undo_slots.rst'
143--- doc/source/scalability/innodb_expand_undo_slots.rst 2012-02-16 10:24:41 +0000
144+++ doc/source/scalability/innodb_expand_undo_slots.rst 2012-06-20 11:16:22 +0000
145@@ -17,9 +17,9 @@
146 * If the expanded slots are used: :command:`mysqld` refuses to start and prints an error in the error log: ::
147
148 InnoDB: Error: innodb_extra_undoslots option is disabled, but it was enabled before.
149- InnoDB: The datafile is not normal for |MySQL|d and disabled innodb_extra_undoslots.
150+ InnoDB: The datafile is not normal for mysqld and disabled innodb_extra_undoslots.
151 InnoDB: Enable innodb_extra_undoslots if it was enabled before, and
152- InnoDB: ### don't use this datafile with other |MySQL|d or ibbackup! ###
153+ InnoDB: ### don't use this datafile with other mysqld or ibbackup! ###
154 InnoDB: Cannot continue operation for the safety. Calling exit(1).
155
156 * If the expanded slots are not used: :command:`mysqld` starts and prints only a warning in the error log: ::
157
158=== modified file 'doc/source/scalability/innodb_io_55.rst'
159--- doc/source/scalability/innodb_io_55.rst 2012-06-04 13:39:55 +0000
160+++ doc/source/scalability/innodb_io_55.rst 2012-06-20 11:16:22 +0000
161@@ -72,7 +72,7 @@
162 This behavior is similar to innodb_max_dirty_pages_pct flushing. The difference is that this method starts flushing blocks constantly and contiguously based on the oldest modified age. If the age exceeds 1/2 of the maximum age capacity, |InnoDB| starts weak contiguous flushing. If the age exceeds 3/4, |InnoDB| starts strong flushing. The strength can be adjusted by the |MySQL| variable :variable:`innodb_io_capacity`. In other words, we must tune ``innodb_io_capacity`` for the ``reflex`` method to work the best. This method was removed in 5.5.20-beta as a fix for bug :bug:`689450`.
163
164 * ``estimate``:
165- If the oldest modified age exceeds 1/2 of the maximum age capacity, |InnoDB| starts flushing blocks every second. The number of blocks flushed is determined by [number of modified blocks], [LSN progress speed] and [average age of all modified blocks]. So, this behavior is independent of the ``innodb_io_capacity`` variable.
166+ If the oldest modified age exceeds 1/4 of the maximum age capacity, |InnoDB| starts flushing blocks every second. The number of blocks flushed is determined by [number of modified blocks], [LSN progress speed] and [average age of all modified blocks]. So, this behavior is independent of the ``innodb_io_capacity`` variable.
167
168 * ``keep_average``:
169 This method attempts to keep the I/O rate constant by using a much shorter loop cycle (0.1 second) than that of the other methods (1.0 second). It is designed for use with SSD cards.
170@@ -223,6 +223,19 @@
171
172 If ``innodb_use_global_flush_log_at_trx_commit=1`` (True), the user session will use the current value of ``innodb_flush_log_at_trx_commit``, and the user cannot reset the value of the global variable using a ``SET`` command.
173
174+.. variable:: innodb_log_block_size
175+
176+ :cli: Yes
177+ :conf: Yes
178+ :scope: Global
179+ :dyn: Yes
180+ :vartype: Numeric
181+ :default: 512
182+ :units: Bytes
183+
184+This variable changes the size of transaction log records. The default size of 512 bytes is good in most situations. However, setting it to 4096 may be a good optimization with SSD cards. While settings other than 512 and 4096 are possible, as a practical matter these are really the only two that it makes sense to use.
185+
186+
187 .. variable:: innodb_log_file_size
188
189 :version 5.5.8-20.0: Introduced
190
191=== modified file 'doc/source/upgrading_guide_51_55.rst'
192--- doc/source/upgrading_guide_51_55.rst 2011-11-25 17:18:03 +0000
193+++ doc/source/upgrading_guide_51_55.rst 2012-06-20 11:16:22 +0000
194@@ -64,6 +64,9 @@
195 * - Multiple Rollback Segments
196 - innodb_extra_rsegments
197 - **(removed)**
198+ * - Dedicated Purge Thread
199+ - innodb_use_purge_thread
200+ - using upstream version
201
202 Shared Memory Buffer Pool
203 ~~~~~~~~~~~~~~~~~~~~~~~~~

Subscribers

People subscribed via source and target branches