> From: André Warnier [mailto:[EMAIL PROTECTED] > Subject: Re: Tomcat threads, II > > We have already tried - because that is one thing we can do - to split > the XML data into smaller chunks, but that does not seem to have any > significant impact.
Nor would I expect it to. The total amount of memory consumed is going to be about the same, regardless of whether or not you split it up. >From the numbers you posted before, it doesn't look like memory is the issue - >you're maxing out the CPU. Parsing XML is very CPU intensive, and you simply >don't have enough cycles to get it done in a reasonable amount of time. If >you can run on a multi-CPU system and figure out how to process pieces of the >XML file in parallel, that would help. > Should I give more/less meory to Tomcat or Java, and if yes how ? Use JConsole to see what's going on while the webapp is initializing. > Can I tell Tomcat/Java to start this application, but use only > some maximum percentage of the memory/cpu time while doing so ? No. You can only limit memory by the -Xmx setting. > I also do not know where to look for the garbage collection log. Likely because you didn't ask for one. Turn on -verbose:gc, and set -Xloggc:<file> to specify the GC logging location. However, I'd use JConsole first - it's easier. > Is there any way, from the outside of the application, that I > can check what exactly the application is busy doing, when it > is starting up ? Again, use JConsole, or turn on JVM profiling (I'd recommend the former). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
