|
From: Vinod P. <vi...@gm...> - 2007-02-14 06:21:51
|
Hi, I'm using wrapper to manage startup and shutdown of a custom server. During performance testing of the server, the profiler reports a lot of cpu utilization in the wrapper methods. To reduce the wrapper communication, I've set the following values in wrapper.conf - wrapper.ping.timeout=0 wrapper.ping.interval=3600 wrapper.cpu.timeout=3600 I know that its not advisable, but this was done to reduce the cpu utilization reported by the profiler. But inspite of this, the profiler reports that SocketInputStream.read() called by wrapper is taking a lot of cpu time. On reviewing the code, I found that there's a loop that reads byte by byte from the wrapper socket. I'm looking at implementing an alternative mechanism that will not cause so much cpu utilization. Suggestions welcome. Regards, Vinod. |