Has anyone done any work in the area of profiling an Elgg instance?
Every now and then our instance will slow down for one reason or
another, and we spend a fair chunk of time scrambling to discern the
cause. Our method usually involves combing apache, php and mysql logs to
try and detect patterns.
It would be nice to have something that monitored Apache, PHP, MySQL
along with RAM, CPU and IO loads to give us a clearer picture as to what
users are doing when slowdowns occur. Does anyone in the Elgg community
have recommendations or current practices they can share?
Thanks.
-Jon