Changes between Version 14 and Version 15 of ServerconfigWebConfigIni

Timestamp:

07/02/10 12:53:39 (14 years ago)

Author:

trevorwekel

Comment:

--

ServerconfigWebConfigIni

@@ -24 +24 @@
 || [#ServerQueueSize Server request queue size] || Tuning the size of the Server request queues ||
 || [#ServerThreadPoolSize Server thread pool size] || Tuning the size of the Server thread pools||
+|| [#ServerCacheSize Server cache size] || Tuning schema and class definition cache ||
+|| [#ServerDataConnectionPoolExcludedProviders Server connection pooling excluded providers] || Tuning connection pooling excluded FDO Providers ||
+|| [#ServerDataConnectionPoolSize Server data connection pool size] || Tuning FDO provider data connection pooling ||
+|| [#ServerDataConnectionPoolSize Server "per provider" data connection pool size] || Tuning per provider FDO data connections ||
+
 === Webconfig.ini ===
 ||'''Parameter'''||'''Description'''||
@@ -127 +132 @@
 == [!FeatureServiceProperties] Section ==#ServerFeatureService
 || '''Property Name''' || '''Supported In''' || '''Restrictions''' || '''Description''' ||
-|| !CacheSize || || 0 < Value <= 5000 || Max # of internal data objects to cache (schemas, classes, etc...) ||
+|| [#ServerCacheSize CacheSize] || || 0 < Value <= 5000 || Max # of internal data objects to cache (schemas, classes, etc...) ||
 || !CacheTimeLimit || || 0 < Value <= 2147483647 || Time duration in seconds for how long to cache the internal data objects ||
 || !CacheTimerInterval || || 0 < Value <= 2147483647 || Time interval in seconds for when the server checks for expired cache entries ||
 || !DataCacheSize || || 0 < Value <= 2147483647 || Max # of features to fetch ||
 || !DataConnectionPoolEnabled || || 0 = disabled, 1 = enabled || FDO connection pooling ||
-|| !DataConnectionPoolExcludedProviders || || 0 <= Length <= 1024 [[BR]]Value = provider name(s) separated by ","[[BR]]Example: OSGeo.SDF,OSGeo.SHP|| The list of providers to exclude from connection pooling. ||
-|| !DataConnectionPoolSize || || 1 < Value <= 1024 || Default # of FDO connections to cache per provider ||
-|| !DataConnectionPoolSizeCustom || || 0 <= Length <= 1024 [[BR]] Example: OSGeo.SDF:10,OSGeo.SHP:10 || Custom # of FDO connections to cache for specified provider ||
+|| [#ServerDataConnectionPoolExcludedProviders DataConnectionPoolExcludedProviders] || || 0 <= Length <= 1024 [[BR]]Value = provider name(s) separated by ","[[BR]]Example: OSGeo.SDF,OSGeo.SHP|| The list of providers to exclude from connection pooling. ||
+|| [#ServerDataConnectionPoolSize DataConnectionPoolSize] || || 1 < Value <= 1024 || Default # of FDO connections to cache per provider ||
+|| [#ServerDataConnectionPoolSizeCustom DataConnectionPoolSizeCustom]|| || 0 <= Length <= 1024 [[BR]] Example: OSGeo.SDF:10,OSGeo.SHP:10 || Custom # of FDO connections to cache for specified provider ||
 || !DataConnectionTimeout || || 0 < Value <= 2147483647 || Time duration in seconds for when an idle FDO connection is dropped ||
 || !DataConnectionTimerInterval || || 0 < Value <= 2147483647 || Time interval in seconds for when the server checks for idle FDO connections ||
@@ -140 +145 @@
 || !DataTransactionTimeout || || 0 < Value <= 1800 || Time duration in seconds for when an idle FDO transaction is dropped ||
 || !DataTransactionTimerInterval || || 0 < Value <= 1800 || Time interval in seconds for when the server checks for idle FDO transactions ||
+=== !CacheSize ===#ServerCacheSize
+The !MapGuide Server uses schema and class definition information in many requests.  Caching this information locally increases server throughput and increases the memory footprint.  !CacheSize controls how many objects the server will cache.  If sufficient memory is available, the !CacheSize should be set to the total number of feature classes visible from all feature sources.
+=== !DataConnectionPoolExcludedProviders ===#ServerDataConnectionPoolExcludedProviders
+By default, SDF data sources do not use pooled connections.  This allows read/write operations to occur.  Some performance improvement can be obtained by enabling connection pooling for SDF and SHP.  Note:  Turning on connection pooling for SDF will make SDF unsuitable for FDO update operations.  If temporary layers are constructed using SDFs, connection pooling must be disabled for SDF.
+=== !DataConnectionPoolSize ===#ServerDataConnectionPoolSize
+Pooled connections allows the !MapGuide Server to reuse existing connections to FDO feature sources.  Database connections are created once and reused for multiple requests.  Typically, two connections per core is sufficient to obtain full utilization of the cores on the !MapGuide Server.  Please note:  Many FDO providers maintain schema for each connection.  This increases the memory footprint as more connections are opened.  
+=== !DataConnectionPoolSizeCustom ===#ServerDataConnectionPoolSizeCustom
+Pooled connections can also be set on a per-provider basis.  This can be used to increase the connection pool for specific providers, like databases, while leaving the other providers alone.  See [#ServerDataConnectionPoolSize DataConnectionPoolSize] for tuning considerations.
 
 == [!MappingServiceProperties] Section ==#ServerMappingService