Modifying a saved resource in a large repository pins the server at 100% for almost a minute.

[stevedang]

We have a repository with about 7000 resources. If a user opens, modifies and saves a feature source for an unmanaged connection for example it takes between 45 and 60 seconds to process the cache cleanup after the save takes place. While this is happening the CPU is pinned at almost 100%.

In this particular case there are practically no session resources, just data resources. The features being edited are related to layers associated with a map that is tiled, but there is no populated tile cache.

If this happens with just one user, the system could become unresponsive if 2 or more Authors were working on resources at the same time.

[stevedang]

Fixed by submission <<​http://trac.osgeo.org/mapguide/changeset/3230>>