Re: Running profiled WOApps

From: Ulrich Köster (ulric..ssense.com)
Date: Tue Feb 25 2003 - 15:07:31 EST

Next message: Kaelin Colclasure: "Re: New user Q: Main.wo not opening properly, says "Could not ope n source file""

Previous message: Ian McDougall: "RE: New user Q: Main.wo not opening properly, says "Could not opensource file""
In reply to: Anders Peterson: "Running profiled WOApps"
Next in thread: Andrus Adamchik: "Re: Running profiled WOApps"
Reply: Andrus Adamchik: "Re: Running profiled WOApps"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
>

Next message: Kaelin Colclasure: "Re: New user Q: Main.wo not opening properly, says "Could not ope n source file""
Previous message: Ian McDougall: "RE: New user Q: Main.wo not opening properly, says "Could not opensource file""
In reply to: Anders Peterson: "Running profiled WOApps"
Next in thread: Andrus Adamchik: "Re: Running profiled WOApps"
Reply: Andrus Adamchik: "Re: Running profiled WOApps"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Tue Feb 25 2003 - 15:10:19 EST