[mapguide-internals] Tweaking serverconfig.ini defaults for 2.1
trevor.wekel at autodesk.com
Wed Oct 8 14:12:03 EDT 2008
I would leave SDF and SHP as excluded. This should ensure that SDF edit use cases remain intact (like measure, buffer, markup, etc). I did some lightweight benchmarking a few weeks ago with a lot of SDF and MapGuide 2.0.2. Turning connection pooling on for SDF only seemed to improve performance by about 5-10%.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, October 08, 2008 10:52 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Tweaking serverconfig.ini defaults for 2.1
In general, I think it would be a good idea to tweak the settings for a
more "normal" installation where you see lots of layers, etc. This
would go a long way towards addressing some of the performance
complaints. Ideally, people would take the time to configure MapGuide
for their expected load, secure it properly, etc, but I doubt this is
all that common.
I think the main problem with not excluding these providers is running
into locking issues when trying to edit the files via MapGuide. I don't
think that this is a common use though. Perhaps including them, and
providing documentation on requirements for editable layers would be a
I think someone (Dave Wilson maybe?) proposed setting up two references
to the providers, one of which wasn't excluded, and only using the
excluded version on RW data sources. I haven't tested this though.
From: Zac Spitzer
Subject: [mapguide-internals] Tweaking serverconfig.ini defaults for 2.1
What do people think about tweaking the defaults for serverconfig.ini?
My understanding is that the CacheSize=100 setting is a bit small for
everything beyond a few basic maps
Also what about the SDF & SHP with DataConnectionPoolExcludedProviders
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals