How big is your main memory? Compiling (both source JIT) consumes lots of
memory. If your main memory is small, it can take a lot of initialization
time!
Gavan Hood wrote:
My web app is very simple, two servlets already installed so no war file.
Once it finally gets going it is very
I agree it will take time, i have 64MB of ram. I guess dotnets ability to
compile on install would be useful here... i don't think there is an equivalent
for java especially 1.4.2 that I am running. Has there been any progress on
that in recent times ? If there is that would be great...
How big is your Java heap? And how much of your 64MB is used by other
(non-Tomcat) processes? If Tomcat is causing a lot of virtual memory
swapping, it *may* help to decrease the size of the heap so it fits
into main memory. But that may make the heap too small, so garbage
collection becomes a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gavan,
Gavan Hood wrote:
| My web app is very simple, two servlets already installed so no war
| file. Once it finally gets going it is very responsive, the
| initialization just takes forever...
A few quick questions:
Do your servlets perform any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gavin,
Er, forget my ravings about SSL initialization. I forgot that you said
you were seeing very high CPU utilization. Waiting for randomness would
not behave that way.
- -chris
Christopher Schultz wrote:
| Gavan,
|
| Gavan Hood wrote:
| | My
Normally compilers are the memory hogs! A few things you can do is that;
1. If you use JSP, convert to servlets to avoid initialization phase
compiling.
2. If your JDk is JIT (Just in time) compiler enable, disable it. You may
have a bit slow execution. But should have satisfactory speed.
3.
From: Gavan Hood [mailto:[EMAIL PROTECTED]
My problem is the initialization.
When I start tomcat it takes about two minutes to complete
initialization and pegs my little processor at times, often
it keeps it around 80% untilized...
Yeah, that's not good in an embedded device!
2 minutes
On Jan 16, 2008 4:21 AM, Peter Crowther [EMAIL PROTECTED] wrote:
From: Gavan Hood [mailto:[EMAIL PROTECTED]
My problem is the initialization.
When I start tomcat it takes about two minutes to complete
initialization and pegs my little processor at times, often
it keeps it around 80%
My web app is very simple, two servlets already installed so no war file.
Once it finally gets going it is very responsive, the initialization just
takes forever...
I have some war files coming, but I figure if I cannt get this basic
initialization to work theres not much point.
