Hrm. ideally, I'd be interested in 4 numbers: 1. Hits per hour, peak time 2. % of those hits delivered by static html rendered from TG (ie, periodic render to disk of mostly-static pages) 3. % of those hits delivered by TG but without touching a database 4. % of those hits delivered by TG with database involvement
Obviously the remainder is purely static stuff like images and plain html (or rendered by non-tg) if you have a load balanced solution, but it's all one site, I'd count the whole lot. If that info isn't available, just the amount actually delivered by TG would be interesting. On Feb 26, 10:35 am, Toshio Kuratomi <[EMAIL PROTECTED]> wrote: > Richard Clark wrote: > > Anyone wanna make a play for the busiest Turbogears-driven site? be > > good to have some big numbers to throw around at clients. > > What are your criteria? > > In Fedora, all of our busy TG apps are load balanced. So do you rate it > as number of hits to the app or per server? > > We have one app that gets hit with a high amount of json traffic at the > beginning of every month when an automated client checks in. > Unfortunately, it doesn't currently survive that so it's not a good > example yet :-) When it does, would that count? It's passing JSON data > up and down so it's different than your traditional view-a-web-page usage. > > I have another application that doesn't get very much intended traffic > (well, except for google :-). However, something is wrong with our > proxy settings so it's getting a huge amount of unintended traffic that > I simply raise redirect to the proper page. Would you count that? > (there's no db access or page rendering...) > > -Toshio > > signature.asc > 1KDownload --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
