Hi Everyone.
I was reading on several forums that using MYSQL 5.5 will be a good option as it improves the performance compared to my current version 5.0.77.
I guess we are able to run things, only because we are using boost to completely cache the server.
I have listed some of the status variables from our website's drupal admin below. Some of them, made me think that something is wrong.
What should we do in order to correct the issues.
Also, our current version of Drupal is 5.23. I have tried many times in the past to upgrade to Drupal 6, but it hasn't finished correctly ever. The number of nodes are too high (250k nodes), so, i am stuck with Drupal 5.
Regards
Dhaliwal
Command counters
Variable Value Description
Com_select 10 The number of SELECT-statements.
Com_insert 0 The number of INSERT-statements.
Com_update 0 The number of UPDATE-statements.
Com_delete 0 The number of DELETE-statements.
Com_lock_tables 0 The number of table locks.
Com_unlock_tables 0 The number of table unlocks.
Query performance
Variable Value Description
Select_full_join 0 The number of joins without an index; should be zero.
Select_range_check 0 The number of joins without an index; should be zero.
Sort_scan 0 The number of sorts done without using an index; should be zero.
Table_locks_immediate 2568358808 The number of times a lock could be acquired immediately.
Table_locks_waited 595959 The number of times the server had to wait for a lock.
Query cache information
The MySQL query cache can improve performance of your site by storing the result of queries. Then, if an identical query is received later, the MySQL server retrieves the result from the query cache rather than parsing and executing the statement again.
Variable Value Description
Qcache_queries_in_cache 10462 The number of queries in the query cache.
Qcache_hits 1683231921 The number of times that MySQL found previous results in the cache.
Qcache_inserts 1450758140 The number of times that MySQL added a query to the cache (misses).
Qcache_lowmem_prunes 1266726191 The number of times that MySQL had to remove queries from the cache because it ran out of memory. Ideally should be zero.