[Seaside] Profiling Code
ssastre at seaswork.com
Sat Feb 2 15:52:26 UTC 2008
maybe a primitive is envolved? MessageTally wont see details about
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Ramon Leon
> Enviado el: Viernes, 01 de Febrero de 2008 21:45
> Para: 'Seaside - general discussion'
> Asunto: RE: [Seaside] Profiling Code
> > On 2/1/08, Ramon Leon <ramon.leon at allresnet.com> wrote:
> > > I'm having a hard time believing that 87% of my render time
> > is spent
> > > in a method that looks like this...
> > >
> > > WAOptionTag>>selected: aBoolean
> > > self attributes at: 'selected' put: aBoolean
> > Do you consistently get this same trace, or was this a one
> time thing?
> > If the Squeak VM wasn't the active process for a while, all of the
> > wall clock time until it became active again will be attributed to
> > whichever method it happened to be in at the time it was suspended.
> > Avi
> It's very consistent, but I think I've figured it out, it's a
> SoapHref proxy #becomeReal getting triggered by the
> #selected:. Not sure why that doesn't show up in the
> profiler, but I think that's what taking up the time.
> Ramon Leon
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside