← Back to team overview

dhis2-devs team mailing list archive

[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 720: Minor

 

------------------------------------------------------------
revno: 720
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Wed 2013-04-03 18:39:50 +0200
message:
  Minor
modified:
  src/docbkx/en/dhis2_implementation_guide_installation.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription
=== modified file 'src/docbkx/en/dhis2_implementation_guide_installation.xml'
--- src/docbkx/en/dhis2_implementation_guide_installation.xml	2013-04-03 15:10:49 +0000
+++ src/docbkx/en/dhis2_implementation_guide_installation.xml	2013-04-03 16:39:50 +0000
@@ -59,9 +59,10 @@
     <para>Do performance tuning by opening the following  file by invoking </para>
     <para><code>sudo nano /etc/postgresql/9.2/main/postgresql.conf</code></para>
     <para>and set the following properties:</para>
-    <para><code>shared_buffers = 2000MB</code></para>
+    <para><code>shared_buffers = 2400MB</code></para>
     <para>Determines how much memory PostgreSQL can use for caching of data. This setting controls
-      how the size of the kernel shared memory which should be reserved for PostgreSQL.</para>
+      how the size of the kernel shared memory which should be reserved for PostgreSQL. Should be
+      set to around 30% of total memory designated for PostgreSQL.</para>
     <para><code>work_mem = 20MB</code></para>
     <para>Determines the amount of memory used for internal sort and hash operations. This setting
       is per connection, per query so a lot of memory may be consumed if raising this too
@@ -72,8 +73,8 @@
       performance of index creation during the analytics and data mart generation processes.</para>
     <para><code>effective_cache_size = 8000MB</code></para>
     <para>An estimate of how much memory is available for disk caching by the operating system (not
-      an allocation) and is used by PostgreSQL to determine whether a query plan will fit into the
-      cache or not. Setting it to a higher value than what is really available will result in poor
+      an allocation) and is used by PostgreSQL to determine whether a query plan will fit into
+      memory or not. Setting it to a higher value than what is really available will result in poor
       performance. This value should be inclusive of the shared_buffers setting. PostgreSQL has two
       layers of caching: The first layer uses the kernel shared memory and is controlled by the
       shared_buffers setting. PostgreSQL delegates the second layer to the operating system disk