[Seaside] My progress with Seaside...

Avi Bryant avi.bryant at gmail.com
Wed Jan 4 20:47:29 CET 2006

On Jan 4, 2006, at 9:44 AM, Jeremy Shute wrote:
> The chiefest of my problems right now is rendering speed, which I  
> misspoke
> about.  The profiler numbers at the bottom show that it takes  
> ~350ms to
> render a ~90K page.  If I search for something on Google (the "bar" in
> terms of user experience) and tack on the &num=50 parameter (where  
> they
> are pumping ~90K to me), it ALSO takes about ~350ms, but their  
> response
> time is almost instantaneous!
> It "feels" slow, but according to the numbers, it's the same.  I've  
> got to
> investigate why.

I suspect this is for one of two reasons, probably a combination of  

- Comanche doesn't offer a way to stream output back to the browser;  
the entire response has to be generated before the browser sees any  
of it.  With google, the browser is getting the top of the page  
immediately and can start showing it to you.  That makes a big  
difference in perceived speed.
- Google is very lightweight in terms of Javascript and CSS, so the  
browser doesn't have to do much work to render the HTML, which again  
means that you can see something right away.

The first problem should be solvable; I've been very careful in  
Seaside's API design not to prevent streaming, but we need to support  
it at the webserver level.  The second one is a tradeoff that has  
nothing to do with Seaside per se.


More information about the Seaside mailing list