On Apr 7, 4:48 pm, Ross Vandegrift <[EMAIL PROTECTED]> wrote: > In other words - make sure the slowness isn't the client :)
I hope this post wasn't serious. Mozilla's CSS rendering engine, doesn't write in our python profile on the server and no, we don't use Mozilla for benchmarking (we are currently using "ab" and "siege"). But to ask otherwise, is there anybody else who has experienced similar performance problems when accessing lots of heavy eagerloaded sqlalchemy models wich are all already in the memory? Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
