In MapGuide 2010, enhanced logging was made available. The MapGuide WIki has the full set of details, but here's my summary. There's a new section in serverconfig.ini: LogsDetail, in the General Properties. For reference, here's the descriptive section:
What does this all mean?
- You can extract a lot more detail about use, errors, and what is going on inside your MapGuide site.
- You stand a chance of filling your drive with logs (up to 100 mb/hr is possible at level 3)
- You can tie usage to users, bringing me to the second part of this post. (depending on how you have logons set up, they may or may not be anonymous users)
MapGuide in a multiple processor/core environment is relatively lightweight when not being called upon. However, depending on the implementation of the site (lots of layers, imagery at all scale ranges, etc), users sometimes will complain of slow performance. The admin will go to the task manager, and lo, with just that user, CPU usage overall is low. This is becuase Mapguide assigns each user to a thread, and each thread to a CPU or processor. This is great for sites with many users. If you want to maximize performance for a small user base, you'll be better off following good practices as if you were expecting a large number of concurrent users, rather than expecting to leverage all cores at once.