MySQL query cache vs caching result-sets in the application layer
        Posted  
        
            by GetFree
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by GetFree
        
        
        
        Published on 2010-05-25T17:35:48Z
        Indexed on 
            2010/05/25
            18:31 UTC
        
        
        Read the original article
        Hit count: 380
        
I'm running a php/mysql-driven website with a lot of visits and I'm considering the possibility of caching result-sets in shared memory in order to reduce database load.
However, right now MySQL's query cache is enabled and it seems to be doing a pretty good job since if I disable query caching, the use of CPU jumps to 100% immediately.
Given that situation, I dont know if caching result-sets (or even the generated HTML code) locally in shared memory with PHP will result in any noticeable performace improvement.
Does anyone out there have any experience on this matter?
PS: Please avoid suggesting heavy-artillery solutions like memcached. Right now I'm looking for simple solutions that dont require too much time to implement, deploy and maintain.
© Stack Overflow or respective owner