Browse code

- remove the note about the PGK_MEM_POOL_SIZE, this is already fixed in the trunk

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@5033 689a6050-402a-0410-94f2-e92a70836424

Henning Westerholt authored on 06/10/2008 10:46:47
Showing 2 changed files
... ...
@@ -187,11 +187,6 @@ Chapter 1. Admin Guide
187 187
    much tested at the moment. In load balancing scenarios the
188 188
    usage of the config file mode is recommended, to avoid the
189 189
    additional complexity that the database driven routing creates.
190
-   Please note: although the routing tree is stored in shared
191
-   memory, for the initial loading from the database on startup
192
-   private memory is allocated. Thus you'll probably need to
193
-   increase the private memory pool size. For 40.000 routing rules
194
-   a "PKG_MEM_POOL_SIZE" of 10 MB is sufficient.
195 190
 
196 191
    Routing tables can be reloaded and edited (in config file mode)
197 192
    with the MI interface, the config file is updated according the
... ...
@@ -25,10 +25,7 @@
25 25
 		more than several hundred thousand routing table entries. It should be able to handle
26 26
 		more, but this is not that much tested at the moment. In load balancing scenarios the
27 27
 		usage of the config file mode is recommended, to avoid the additional complexity that
28
-		the database driven routing creates. Please note: although the routing tree is stored
29
-		in shared memory, for the initial loading from the database on startup private memory
30
-		is allocated. Thus you'll probably need to increase the private memory pool size. For
31
-		40.000 routing rules a <quote>PKG_MEM_POOL_SIZE</quote> of 10 MB is sufficient.
28
+		the database driven routing creates.
32 29
 	</para>
33 30
 	<para>
34 31
 		Routing tables can be reloaded and edited (in config file mode) with the MI