|
From: Leif M. <le...@ta...> - 2004-01-08 06:03:52
|
Elhanan,
Please post tot the Wrapper users list rather than to me directly.
This lets others
answer your questions and makes the mail searchable so others can learn
from it in the
future.
אלחנן מעיין wrote:
> Hi.. after running our java program on it's normal mode and running it
> as a service we noticed there is a difference in performance between
> the two (the first takes around 2-3 seconds, and as a service takes 8
> seconds) any ideas on what's creating the laaag?
>
I am going to need more information to be able to give you any
useful answers.
When is the service being run? At startup? Is it possible that the
service is competing for
system resources etc?
The only difference in performance that I am aware of is actually
the other way around.
If an application sends large quantities of output to stdout then the
Wrapper, and a
standalone JVM for that matter, sends all of that information to the
console. Windows
is pretty slow in the way it displays text in a command window and
quickly becomes a
bottle neck as it tries to paint all of the text, in graphics mode, in
real time.
When running as a service, there is no console so all of that output
is just thrown away.
In both cases, writing to a log file is very fast.
Could you try enabling debug output and run a single run in Console
mode and then
again as a Service. By comparing the timestamps in the log files it may
become obvious
if a particular action is taking a lot of time or if the application is
in general running slower
as a service.
I have not seen this behavior but I'll do a few tests to get some
numbers.
Cheers,
Leif
>
> This mail was scanned and found secure
>
> The contents of this email and any attachments are confidential.
> It is intended for the named recipient(s) only.
> If you have received this email in error please notify the sender
> immediately through the
> technological support center,email:he...@mi... and do not
> disclose the contents to any one or make copies.
>
>
|