Re: [Wrapper-user] Performance issues

[Vinod P. <vi...@gm...>]

OK, I ran the application with cpu sampling and tracing and with debug enabled.

According to the code, if there is communication, there should be a
log message in wrapper.log.  There's nothing of that sort, which means
that handleSocket() is not getting invoked.

During sampling, the profiler is reporting cpu usage in the
handleSocket() method call.  During tracing, it shows that the method
has been invoked just once.

Does this make sense to anyone?  Does it look like an issue with the profiler?

Regards,
Vinod.

On 2/15/07, Vinod Panicker <vi...@gm...> wrote:
> On 2/15/07, Leif Mortenson <le...@ta...> wrote:
> > Vinod,
> > >From your profile output, it shows that of the CPU time that your
> > application consumed, 23% was being consumed by the Wrapper reading
> > from the socket you mentioned, and the remaining 77% was being
> > consumed by the ThreadPoolExecutor. I assume this is where your
> > application is running.
>
> Thats right.
>
> > This represents the Wrapper consuming a total of 48.5s of CPU time.
> > For reference, how much actual time was the JVM running for? While
> > this may look bad, it may simply be a matter of the JVM as a whole being
> > quite idle.
>
> In the telemetry, Yourkit is showing that the JVM ran for 3 minutes.
>
> > I have profiled other applications in the past and while the Wrapper
> > registers on the list, it is always near the bottom as far as CPU usage.
> >
> > Reviewing the code, I also do not see any reason why this should be
> > consuming very much code.
> >
> > If the the 48.5s CPU time is building up over a show actual time frame
> > then it means that that loop is thrashing somehow. If so, this would be
> > made obvious by enabling debug output by setting the following property
> > in the configuration file:
> >
> > wrapper.debug=true
>
> This should do the trick.  Let me try it out and let you know.
>
> Regards,
> Vinod.
>