Browse code

- add a note about PKG_MEM_POOL_SIZE requirements for larger number of routing rules during startup

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

Henning Westerholt authored on 08/09/2008 11:14:13
Showing 2 changed files
... ...
@@ -182,6 +182,11 @@ Chapter 1. Admin Guide
182 182
    much tested at the moment. In load balancing scenarios the
183 183
    usage of the config file mode is recommended, to avoid the
184 184
    additional complexity that the database driven routing creates.
185
+   Please note: although the routing tree is stored in shared
186
+   memory, for the initial loading from the database on startup
187
+   private memory is allocated. Thus you'll probably need to
188
+   increase the private memory pool size. For 40.000 routing rules
189
+   a "PKG_MEM_POOL_SIZE" of 10 MB is sufficient.
185 190
 
186 191
    Routing tables can be reloaded and edited (in config file mode)
187 192
    with the MI interface, the config file is updated according the
... ...
@@ -25,7 +25,10 @@
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.
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.
29 32
 	</para>
30 33
 	<para>
31 34
 		Routing tables can be reloaded and edited (in config file mode) with the MI