I noticed the same thing awhile back. Most of my tables have over 600 records and one has over 2400. It's about 15 seconds to display a good sized page. The delay was one of the reasons the thread on pagination interested me. I use that method now. I also provide a 'view all button' for those who love Ctrl-F. It presents a 'this may take a while' message while chugging away:

http://trac.turbogears.org/turbogears/wiki/Search_Pagination

I hope this helps,

Nick

On 4/17/06, Steve Bergman <[EMAIL PROTECTED]> wrote:

Thanks for the reply.  I'm printing to stderr to monitor what parts
finish when.  I know that SQLite is finished in about 0.5 seconds.  My
method, which puts all the data in a list and sorts it, is finished in
another 0.5 seconds or so. (The list() and sort() would force SQLObject
to cough up all the data, so I know I'm not being confused by lazy
evaluation.)

The several second delay is definitely after I have passed my
dictionary to Kid/form.display().

Not a show stopper, but it would be nice if it had a little more snap
to it.  Knowing how the Python community discourages premature
optimization, I suspect that this will get faster with future releases.



G-Mail Account
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to