> Does anyone have suggestions as to testing and rolling-out practices for > TG sites? Furthermore, is anyone running a TG site across multiple > machines, serving requests in parallel?
Even on one machine, I find that something like 2 TG processes per processor gives the best performance for our app. And you can update one process at a time as long as your DB schema doesn't change (assuming you don't have other shared state issues). We our servers don't generally get updated except at scheduled update times, so I don't generally do this, but you can :) > If so, I would love to open up > a dialog with you. I'm particularly curious about practices for > synchronised restarting of servers after code upgrades, and for avoiding > the down-time that involves. > > My first (and only, to date) high-traffic TG site was coded to run > across multiple machines. It uses no local caching, and uses memcached > for everything. > > This required the use of Cheetah, however. Which is not ideal, since > one cannot yet code widget templates in Cheetah. This requires the use > of two template languages, which my employer certainly won't like. I'd suggest using ToscaWidgets if you can't use Kid (which unfortunately is the case on high traffic sites that can't do rendered page caching) as it will let you use Mako or Cheetah or whatever template engine you want in widgets. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
