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