[Seaside] Rendering text in ShoreComponents-2.6-pk.9 is 5 times slower than built-in canvases

John Pierce john at pierce.name
Thu Apr 27 01:21:34 UTC 2006

Hi all,

I'm having a hard time using ShoreComponents on some of my larger text
pages. Pages that normally take 3 - 5 seconds to return to my users
using WARendererCanvas or WAHtmlRenderer classes takes upwards of 15 -
30 seconds to return the same page using ShoreCanvas.

I had to turn off CPUWatcher as well as it was putting up a modal
window on my page request and blocking the response to the user.

Attached is a changeset that implements a timing page that
demonstrates what I am seeing. The following page using the built-in
renderers returns in 3 to 4 seconds on my box and using ShoreCanvas,
returns in 15 - 20 seconds.

Maybe there is nothing to do to tweak ShoreCanvas, but it is making it
difficult to return some tables that 400+ rows on one page for me.

Some might say just break my page up, but, really, it doesn't end up
being much data to work with and it seems to be okay using the
built-in Seaside renderers so if this is fixable that'd make my
implementations a bit easier.



The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore, all
progress depends on the unreasonable man. -- George Bernard Shaw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TooMuchDataWebPage.st
Type: application/octet-stream
Size: 2358 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20060426/4774af34/TooMuchDataWebPage.obj

More information about the Seaside mailing list