Re: Monitoring large resultsets

[Jerome Benezech]

Thanks for the tips.
As I said, I am aware of the improvements needed in indexing and coding, but the app being several layers of joomla extensions, this is going to take a long time to optimize the code.
This is actually not my server, I've been asked to look into it as they have perf problems.

My immediate worry is that the linux server is going down and I'm trying to figure why. Certainly queries need to be optimized and the bad implementation is taking its load on the machine. But I'd think a box with 12GB of RAM and 8 cpus, would handle a few concurrent queries, even with poor coding. So there is something else going on.
As I said, php processes are taking a lot of mem and cpu and I suspect there is a connection between big resultsets being retrieved. With this multi layer joomla cake it is difficult to find where this happens and I hoped I could identify the big resultsets from the mysql side.