Dear Nate,
I am porting an application from Windows to Linux which makes heavy
use of
servlets. I have a fairly intensive background process (currently a
windows
service) that requires no user interaction. I plan to rewrite the
code in
Java and I am wondering if there is any notable performance difference
between running the Java code under Tomcat as opposed to running the
code
directly as a daemon.
No there is not. Tomcat just handles the HTTP serving part and the
processing is done in Java, just as it would it it were a Tomcat-less
JVM.
Since the application requires Tomcat, I know I can
code it up as a servlet and kick off the processing in the init()
function
and not worry about executing the code directly as a daemon. Since
this is a
performance sensitive process I want to make sure that I choose the
optimal
route.
Performance is determined by many factors.
Does anybody know how java code running as a servlet compares
performance-wise to the same code running as a daemon? Is one way
generally
better than the other?
No difference. You'd need something that handler HTTP access to your
servlet, so you'd wind up with something like Tomcat anyway.
I think you have a strange idea of what a daemon is. After all, most
of us run Tomcat as a daemon.
--
Kees Jan
http://java-monitor.com/forum/
[EMAIL PROTECTED]
06-51838192
The secret of success lies in the stability of the goal. -- Benjamin
Disraeli
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
