|
From: Leif M. <le...@ta...> - 2009-03-27 10:21:40
|
Zeynep, It is never a waste of time. I am glad you got things working. Let me know if there is anything else we can help out with. Cheers, Leif On Fri, Mar 27, 2009 at 5:44 PM, Gunal, Zeynep <zey...@tr...> wrote: > Thank you for your reply. Our test team applied your sugegstions, and > they reported no improvements. Only then when I looked into the log > files I was given to send you I realized that I lied in my first e-mail, > because although I thought the java heap size was increased, it was > actually not done. > The service is running as expected and there is no performance issue. > I apologize for wasting your time. > Regards, > Zeynep > > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: 24 March 2009 18:30 > To: wra...@li... > Subject: Re: [Wrapper-user] Wrapper service performance question > > Gunal, > Could you try setting the wrapper.java.command.loglevel=INFO property > so the generated java command will be output to your logs. Then run > the Wrapper in console mode and as a service to make sure that the > correct JVM is being run. > > A common problem is to not add the correct JVM onto the PATH of the > system user. This results in the default java that ships with Windows > being run. > > The Wrapper itself does not do anything which would affect the > performance of the Java process. One way to prove this is to copy the > above java command line into a batch file, remove the -Dwrapper.key > system property, then run the batch file manually outside of the > Wrapper. If you still see the slowdowns there then the problem can > be narrowed down to the parameters being passed to the JVM. > > Attach your wrapper.conf as well as the generated java commands above > and I might be able to help out more. > > Cheers, > Leif > > 2009/3/25 Gunal, Zeynep <zey...@tr...>: >> Hi, >> >> >> >> We have noticed that it is taking longer for the service to process > the same >> input than when the application is run from the command prompt. >> >> >> >> For instance, processing a 39MB file from the command line took 4 >> milliseconds but it took 12 minutes to process the same file with the >> service. >> >> >> >> Also, the service seems to slowdown as more data is processed, for > example >> the number of records processed go from 204 in the first minute to > 12/min >> after 57 minutes! >> >> >> >> We increased the java heap size, we disabled the console logging > level, this >> behaviour did not change. >> >> >> >> Did anybody have a similar experience? Any suggestions? We are feeling >> hopeless! >> >> >> >> Thanks. |