Hi Ramdas, > I have a web site where around 15 SQL semi complex queries run on the home > page. Traffic is increasing and the page loads are getting slower. What is > the best way to cache just the home page. I have already done standard > memcached on the server.
I'm still learning about caching so forgive/correct any wrong suggestion :) I use memcached on a small to medium size site, the bottleneck here was RAM usage, I think if you can get enough RAM space, memcached is the best choice. I made a script to generate the homepage every x minutes and serve it through nginx, I don't have too much RAM :) > Please suggest the best caching options, where we can have page loads (home > page is about 100 K with the ads). I have fine tuned everything possible > from client side, like minimifying javascripts/css files and using right > graphic formats. What do you want to save? Band? Processing? Memory? I think cache will saves you processing, once you don't hit the database every time. This way the user gets the page faster, as he don't need to wait database read... Has you homepage user related data? In another portal I have a login widget that shows a login form if the user isn't authenticated or a grettings message with user information if it is logged in. Once I made the homepage static, to have the user dependant widget, I call it through ajax/jquery Hope I could help you! Best regards -- Michel Sabchuk http://turbosys.com.br/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
