Zope slowdown publishing big tables
Hi, I have recently written a few pages which either generate or contain large html tables. I started to notice some fairly substantial slowdown with tables over 100 or so rows. At a guess, I assume this is zope rendering all the <tr> and <td> tags looking for dtml, but it seems a bit slow even for that. We're running pretty substantial servers with plenty of memory, etc. I'd be interested in any good ways to improve the speed of these pages. The obvious answer would be caching, but I'd rather avoid the complications that entails if possible. I'm more interested in what Zope's really doing to slow itself down here. TIA -- Alex This e-mail and any attached files are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication represents the originators personal views and opinions, which do not necessarily reflect those of The Royal College of Surgeons of England. If you are not the intended recipient, or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. http://www.rcseng.ac.uk Registered Charity Number: 212808
Note that nested tables are notorious for appearing to be "slow" on most browsers because the browser needs to render each table before showing anything else on the page. I'd suggest benchmarking the page generation time with something other than a browser (e.g. Apache's "ab") to ensure that it's Zope's fault and not the browser's if you haven't already. On Tue, 2003-09-02 at 10:53, Luton, Alex wrote:
Hi,
I have recently written a few pages which either generate or contain large html tables. I started to notice some fairly substantial slowdown with tables over 100 or so rows. At a guess, I assume this is zope rendering all the <tr> and <td> tags looking for dtml, but it seems a bit slow even for that. We're running pretty substantial servers with plenty of memory, etc.
I'd be interested in any good ways to improve the speed of these pages. The obvious answer would be caching, but I'd rather avoid the complications that entails if possible. I'm more interested in what Zope's really doing to slow itself down here. TIA
-- Alex
This e-mail and any attached files are confidential and are intended solely for the use of the individual or entity to whom they are addressed.
This communication represents the originators personal views and opinions, which do not necessarily reflect those of The Royal College of Surgeons of England.
If you are not the intended recipient, or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited.
Registered Charity Number: 212808
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Chris McDonough <chrism@zope.com> Zope Corporation
Alex, I've noticed this as well, but after a fair amount of experimentation, I've come to the conclusion that the problem is more the browser's rendering abilities than Zope. Of course, you could test this by saving out the source of the rendered page and comparing the time required to load this page from, say Apache to the time required to serve it from Zope. That said, Zope has a number of ways in which the caching of pages can be tweaked and optimized. One of them may be just the ticket. Also, try to avoid nested HTML tables.. and make the code for your pages as simple as possible..
Hi,
I have recently written a few pages which either generate or contain large html tables. I started to notice some fairly substantial slowdown with tables over 100 or so rows. At a guess, I assume this is zope rendering all the <tr> and <td> tags looking for dtml, but it seems a bit slow even for that. We're running pretty substantial servers with plenty of memory, etc.
I'd be interested in any good ways to improve the speed of these pages. The obvious answer would be caching, but I'd rather avoid the complications that entails if possible. I'm more interested in what Zope's really doing to slow itself down here. TIA
-- Alex
participants (3)
-
Chris Beaumont -
Chris McDonough -
Luton, Alex