Hi guys, > You're not going to get any meaningful feedback by looking at high > profile sites, because you don't know if the backend is similar to yours > or what they did for scaling.
Alexandru is right. The server arrangement can speed up your performance. > I'm currently developing a custom-CMS for a local organization, and I've > optimized the shit out of it ... because we are expecting for the > website's link to be placed on a couple of popular sites. So I am :) > The main problem is the DB access, but Django has a good caching API ... > For caching I'm using MySql instead of Memcached, at least for now (it's > more economic, more flexible, and I'm not doing sharding yet). I do not touch cache yet on my CMS but I'm about to use memcached on everything. I will cache the entire page when it's saved and get it from the cache on rendering (on a view or even directly on the nginx). > as a caching mechanism, practically I've reduced ~ 30 complicated > queries to 5 or 6 simple and very efficient queries. Wouldn't it be better to cache on the RAM? This way you won't need even these queries... I'm not a cache specialist, let me know if I miss something ;) 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 django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
