|
From: Hubert F. <hub...@ab...> - 2007-02-14 13:57:36
|
Hi, Hmm, I tried this with YourKit Java Profiler and didn't notice anything remarkable. I suppose you talk about WrapperActionServer.java. Looking at the code I saw, that the regarding section you mentioned, is called with a timeout of 15 seconds. A command to read consists of just one byte. A cannot see why this thread should generate much CPU utilisation neither could my profiler. Regards hub >>> "Vinod Panicker" <vi...@gm...> 14.02.2007 07:21 >>> 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. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |