Let me add my 2 cents :-).
While profiling during development may give you early and important
insights into various inefficiencies, it is very important to profile
under real production load.
In a multithreaded, multiuser environment, you will discover things you
will never see on your single user development instance or a slightly
loaded test environment. For example, threads waiting for shared resources
to be released may become the biggest bottleneck.
Of course turning on profiling in production will slow down the system,
but this is sometimes unavoidable. Here we do it for say 1/2 an hour after
every major release. (Admittedly the system I am referring to is an
extremely high volume messaging system, not written in WebObjects).
Andrus
> Hi,
>
> I've seen no difference between running a profiled or a 'normal'
> woapplication.
>
> Profiling requires some memory and cpu but for me this okay for the
> value I get.
>
> ulrich
> Am Dienstag, 25.02.03 um 19:39 Uhr schrieb Anders Peterson:
>
>> Hi,
>>
>> Profiling only works when you debug, not when you run.
>>
>> What if my launch configurations are always "profiled"...
>>
>> 1) Is running a Profiled WOApplication any different from running just
>> a WOApplication?
>> 2) When debugging what's the penalty for that extra information I get
>> with the Profiled WOApplication? Is it mainly memory or cpu
>> consumption - how much?
>>
>> /Anders
This archive was generated by hypermail 2.0.0 : Tue Feb 25 2003 - 16:34:14 EST