[Seaside] Performance issue
Philippe Marschall
philippe.marschall at gmail.com
Thu Aug 31 12:43:39 UTC 2006
2006/8/31, Cédrick Béler <cbeler at enit.fr>:
>
> >
> > Profile it so you know where the bottlneck is.
> ok... so directly from seaside ?
>
> do we have to add all times
>
> 91.5% {45ms} SUPSession(WASession)>>incomingRequest:
> |91.5% {45ms} SUPSession(WASession)>>responseForRequest:
> | 91.5% {45ms} SUPSession(WASession)>>performRequest:
> | 91.5% {45ms} SUPSession(WASession)>>start:
> | 91.5% {45ms} WARenderLoopMain>>start:
> | 91.5% {45ms} WARenderLoop>>run
> | 91.5% {45ms} WARender>>go
>
> -> 45 + 45 +45 + ...?
>
> 47 tallies, 49 msec.
No, that's 45 ms total rendering time!
75% or 38ms are spent in EFFormComponent>>#renderRowForSelector:on:
So rendering speed is not your problem. It's either the callbacks or
the network latency. The 3.9 Unix VM is said to have a greatly reduced
network latency. You can try it but I doubt it's that extreme.
I'd say invesitgate your callbacks.
Philippe
More information about the Seaside
mailing list