might be worth bumping these default numbers up? the original numbers were set for resource limited computers almost ten years ago
On Thu, Nov 28, 2013 at 8:54 PM, Jackie Ng <[email protected]> wrote: > To give you better insight, this is what MapGuide caches on the > server-side. > > - Feature Source documents > - Spatial Contexts > - Feature Schemas > - Class Definitions > - Identity Properties > > Of your 320 layers, you have to ask yourself: > > - How many feature sources all these layers point to in total? > - Of this set of Feature Sources: > - Are they flat-files? (generally one class per feature source) > - Are they relational databases (one class for each table per feature > source) > - Are you serving this data in various coordinate systems (one spatial > context per CS) > > Based on this information you can roughly tally up the number of > potentially > cacheable items and set the cache size appropriately. > > Hope this helps. > > - Jackie > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Optimizing-Mapguide-Server-Cache-Size-tp5091621p5091633.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer +61 405 847 168
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
