Re: Monitoring large resultsets

[Jerome Benezech]

Thanks for the help.

Linux RAM is 12 GB. But 3GB used by DNS, so 9GB available between mysql/php/apache/other

News are updated once a day so not much write but your first explanation rang an alarm in my head. There are 2 tables that are being constently updated. Something about hit counter on external agencies adverts, and that happens on every single page. I thought tables are small, only used there...
If I understand you correctly, this means that the 2GB cache is being scanned all the time. For test purpposes, is there a way to specify "no cache" on these 2 queries or tables to make sure there is no cache scan happening then ?


For ISAM, probably can change a lot to INODB but again very little write (once a day).

Regarding queries, I know very poor implementation. I share your point of view regarding 3rd party stuff. The ijoomla_archive component for example is one of the worst example of coding I've ever seen. That's why I usually write my own stuff for my own apps :)