Ok, I'll throw my $0.02 in, although my production site is currently running TG1. I did some testing with TG2 and I think the general concepts around these questions can be applied to both versions.
On Friday 29 May 2009, cd34 wrote: > What are some sites using TurboGears 2.0 in a production setting? > > Is the site Forward Facing or a backend? Facing forward. > How is the site deployed? (mod_wsgi, mod_python, apache2, proxy, > paster, etc) Currently nginx as load balancer distributing the load on 4 cherrypy instances. For TG2 this would be paste, which is faster than cherrypy V2 used in TG1 > What templating engine is used? (Genshi, Mako, Jijna, etc) Genshi. > How have web designers reacted to the constraints placed with the > templating engine you used? Web designers? Hehe. Ok, I'm not a web-designer, but I wrote all the stuff myself. I doubt a web-designer will face a lot of issues. The design is generally something you put into place and then have someone who can program set up the templates. Genshi templates are very easy and require only basic programming skills - hey, even my wife can handle that and she's not a programmer (although she has a decent understanding of HTML and CSS) > Are static files served by TG2? No. Static files are served by nginx with a separate subdomain for images (the site is image-heavy). Subdomains for things like images are generally a good idea, because most browsers have a limitation towards how many concurrent connections they use for one domain (usually a max of 4). If you have images or videos served from a second domain you can get browsers to open more concurrent connections. Broadband gives most users the bandwidth to do that, so in the end your page loads faster for a better user-experience. > How much daily traffic are you seeing? (hundreds, thousands, tens of > thousands) Depending on the day it goes up to 80.000 pages a day with about 60 hits per page. > What type of hardware/hosting? (virtual, virtual machine, dedicated, > cluster, etc) Dedicated servers.Two dual dual-core (4 cores total) machines with 4GB memory each. Another two virtual dedicated servers for image and ad-serving. > What implementation issues have you run into? Not a lot with TG1. Porting to TG2 will take a bit of a rewrite, particularly in the area of SA (their API changed, so using the newer version requires rewriting all queries) and identity handling. Neither of the two should be an issue if you start out with TG2. > What steps have been taken to plan for the thundering herd? The setup allows to just plug in more servers. The website is unlikely to grow suddenly, it's more a "permanent growth over time" kinda site. Particularly with the recent change to avoid Genshi "match" tags (suggested by Mark Ramm), we now can handle roughly 100.000 pages a day. The moment we hit 80.000 a day on a permanent basis we'll just add another server and load-balance with nginx or pull the database onto another dedicated server. In a TG2 setting I'd do some stress testing with mod_wsgi. It's supposed to be faster from what I read. Be aware that TG (either version) is memory hungry like many other similar app-engines/frameworks. So plan on as much memory as you can get within your budget. We started with 2GB memory per machine but had to upgrade to 4GB after a couple of months. Also consider your database in that calculation. Budget permitting I'd opt for a separate database server that is directly LAN connected to a second NIC of the servers. That way you'd have one machine just to handle database. In a combined setup (as we currently use), you have to up the memory to allow for decent database performance - that also depends on what database you use (we use postgresql for many reasons, consistent performance being one of them, having many features that you can trust your payroll with being another. Mysql never was a choice for us. It's faster in simple read-operations, but IMHO lacks seriously when it comes to data integrity and error checking. But that's a discussion for a database list) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
