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

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: no longer in the source branch.
Merged at revision: 714
Proposed branch: lp:~hrvojem/percona-server/bug1392253-5.5
Merge into: lp:percona-server/5.5
Diff against target: 46 lines (+6/-6)
1 file modified
doc/source/performance/innodb_numa_support.rst (+6/-6)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug1392253-5.5
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+241811@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/performance/innodb_numa_support.rst'
2--- doc/source/performance/innodb_numa_support.rst 2013-09-26 13:52:26 +0000
3+++ doc/source/performance/innodb_numa_support.rst 2014-11-14 14:49:14 +0000
4@@ -4,7 +4,7 @@
5 Improved ``NUMA`` support
6 ===========================
7
8-In cases where the buffer pool memory allocation was bigger than size of the node, system would start swapping already allocated memory even if there is available memory on other node. This is would happen if the default :term:`NUMA` memory allocation policy was selected. In that case system would favor one node more than other which caused the node to run out of memory. Changing the allocation policy to interleaving, memory will be allocated in round-robing fashion over the available node. This can be done by using the mysqld_safe :variable:`numa_interleave` option.
9+In cases where the buffer pool memory allocation was bigger than size of the node, system would start swapping already allocated memory even if there is available memory on other node. This is would happen if the default :term:`NUMA` memory allocation policy was selected. In that case system would favor one node more than other which caused the node to run out of memory. Changing the allocation policy to interleaving, memory will be allocated in round-robin fashion over the available node. This can be done by using the mysqld_safe :variable:`numa_interleave` option.
10
11 Another improvement implemented is preallocating the pages in the buffer pool on startup with :variable:`innodb_buffer_pool_populate` variable. This forces ``NUMA`` allocation decisions to be made immediately while the buffer cache is clean.
12
13@@ -22,7 +22,7 @@
14 .. variable:: innodb_buffer_pool_populate
15
16 :cli: Yes
17- :conf: No
18+ :conf: Yes
19 :location: mysqld
20 :scope: Global
21 :dyn: No
22@@ -32,12 +32,12 @@
23
24 When this variable is enabled, |InnoDB| preallocates pages in the buffer pool on startup to force ``NUMA`` allocation decisions to be made immediately while the buffer cache is clean.
25
26-Command-line Options
27-=====================
28+Command-line Options for mysqld_safe
29+====================================
30
31 .. variable:: flush_caches
32
33- :cli: No
34+ :cli: Yes
35 :conf: Yes
36 :location: mysqld_safe
37 :dyn: No
38@@ -49,7 +49,7 @@
39
40 .. variable:: numa_interleave
41
42- :cli: No
43+ :cli: Yes
44 :conf: Yes
45 :location: mysqld_safe
46 :dyn: No

Subscribers

People subscribed via source and target branches