Currently tgext.admin has not been optimized at all for performances and as you noticed it retrieves every related object instantly. I tend never to use it with more than a few hundred records, when I need to manage big collections I tend to write custom get_all methods.
There is for sure an huge space for optimizations in sprox on that topic right now. I'll try to give a look as soon as possible but I cannot guarantee you to roll out a new release in a short time as that is a part of sprox that I didn't write myself. On Thu, Sep 6, 2012 at 12:01 PM, Juraj Variny <[email protected]> wrote: > Hi, > > does here anybody actually use admin extension with meaningful amounts of > data? When I started having 1000+ records in test database, just listing > them took several seconds. I have looked with debugger what it is doing and > it seems that: > > * Regardless of paging, all records in the table are fetched and for every > one record extra select query is done > * If there is one-to many relationship, also all records from related table > are fetched and for every one record extra select query is done > > Or tgext.admin is meant to be this way and I have it badly configured? This > happened both with sqlite and postgres. > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/turbogears/-/hGZLwVYcVDEJ. > 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. -- 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.
