On Wednesday 11 June 2008 17:17:36 Artur Siekielski wrote: > On Jun 11, 11:53 am, [EMAIL PROTECTED] wrote: > > if u replace back the offending function with its plain pythonic > > variant, will it work? > > Which function do you mean? sort_table or whatever it was.
> > 50% boost... just because of the python? u're constructing too > > many queries over and over. > > No, the main module in which we have 50% performance boost is > mostly "number crunching" code which Psyco optimizes very good. > Though SA engine is called quite often, there are about 20 INSERTs > per second. why u psyco the SA code then? psyco should be able to only compile certain things, and leave all else out. i've used it 4 years ago so cannot say more but it was like that even then. or do u mean that when psyco callsback python from assembly, all goes to hell? > > try cache them, and reuse as building > > blocks... - or cache their results... > > We use caching. BTW, something like builtin caching would be nice, > eg. we have a few tables with practically constant content (they > are like ENUM values) and they could be loaded once per application > run. caching of queries themselves does ot mean caching of the results of their execution - u choose which one. svilen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
