let me explain a little bit. we have a news portal in turkey which is fairly new but have a huge improvement by the number of visitors and members. we wanted to keep statistics of how many users we have, where they are and what they are doing so i have pulled up together a pyramid app which runs 3 queries depending of the state of the member. 1) if the member is a new member, add him/her to daily_visitors table which we keep a unique number of visitors and then keep the info of visitor in memcache. 2) add the user to visitors table if he's just come in. 3) if user is already in visitors table for 45 seconds, update where s/he is and what s/he's doing and his visit_time.
this application is connected to the news portal via iframe. so every visitor to the portal is a visitor to this app. so after tv commercials the news portal was getting huge amount of requests so the statistics app was getting that requests as well. so if tg can handle this then this is great because i'm going to re-write the application. On Jul 3, 2:01 pm, Christoph Zwerschke <[email protected]> wrote: > Am 03.07.2011 12:13 schrieb Mengu: > > > well, unfortunately i had 15k reqs/sec because we had advertorials > > running on tv people were jumping in. pyramid could handle it up to > > 30K. as i have said the server was great. even with the 15k reqs the > > loads were very very low. > > That's not really the kind of things that TG was designed for. It is > intended to be used for more or less complex, interactive web apps, > usually stuff where the database queries are the real bottleneck. > > -- Christoph -- 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.
