Thanks Malcolm, I think I've find the issue. I set time.time() to
test several steps in my program, retrieving data is pretty fast, the
entire function spent 6s to finish the task. However, at the final
stage on template rendering, seems Explorer(IE) will be under highly
loaded status(not responding in a long time) if there were so many
records, for example, I use css+div to display all records as a table,
so, for every cell, at least one <li> tag should be included. Say,
there are more than 2,000 records, and every records has rough 20
column. The actual time that IE spent will be extremely longer than
6s.
For double testing above-said reason, I just keep all program and just
remove the FOR looping in my template, the result is faster than
before. However when I set time.time() for testing such FOR looping in
my template ( {% for objs in list_objs %}<ul>{{objs|safe}}</ul>{%
endfor%} ), the total spending time on this is also pretty fast.
Hence, I guess the reason why my application is too slow on showing
thousand of records is that, Explorer(IE) need to spend lots of time
on parsing so many records. (Firefox is a lit bit more faster than IE,
but, the result is still unsatisfied)
I'm just a newbie, hopefully, some Guru can give me a confirmation on
this observation, thanks a lot!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
