I was wondering if there was anything special that needs to be done when using Mapguide 1.2 with base layers and tiling? Under that setup, I consistently get over 40 million page faults for the mgserver.exe process over a 4 hour period of usage.
While a page fault might not be catastrophic, Mapguide is also painfully slow. The machine running Mapguide has 2 Gigs of RAM and a dual core CPU. There is no reason for Mapguide to generate so many page faults. Is there anything in the Mapguide settings that needs to be set so that I can improve its memory management perfomance and stop getting so many page faults? In addition, I have developed a small application that pre-builds the tilecache by just using the Rendering Service and getting the tiles at the proper Row/Col index. This application has been running on our production servers for the last 16 hours and the mgserver.exe is now at a huge 750 million Page Faults. The memory usage has also been steadily climbing and it went from 75 megs to 200 megs over those 16 hours. The server has been doing nothing but serve tiles. So I very likely leaked a little more than 100 megs in 16 hours. That seems a bit excessive. -- View this message in context: http://www.nabble.com/Page-Faults-tp15836139s16610p15836139.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
