I turned on CherryPy's profiling and took a look at the results. I'm not really sure what I'm looking at though. From what I can tell the majority of the time is spent on the database, but it may just be that the database.py module calls a lot of other functions.
I'm using Apache with a proxy. I've tried just loading content directly from port 8080 and the delay is the same, so I'm pretty sure the problem is on Turbogears' side One thing I noticed earlier tonight is that I'm not really using widgets correctly in some places - I'm instantiating a new widget for each request instead of passing values to the display() method. -ryan On May 5, 8:19 pm, "Tim Lesher" <[EMAIL PROTECTED]> wrote: > On 5/5/07, kerinin <[EMAIL PROTECTED]> wrote: > > > > > I'm averaging about 1.5s / page. My site is not particularly complex > > - I have about 5 main classes in my model with some supporting stuff > > and 4 main controllers. Nothing really fancy. I was using MySQL but > > I switched to SQLite to try to speed things up. > > You won't know where your problem lies until you do some profiling. > Compare serving static pages, serving a quickstarted site that doesn't > hit the DB at all, etc. > > You also haven't mentioned what HTTP server you are using, or how your > interfacing the TG service with it--those are going to potentially > change the answer as much as or more than page optimizations will. > > -- > Tim Lesher <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
