Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

emacs, er, Java makes all computers slow More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

not that java ain't a pig... (Score:2)

by lachoy (1663)

...but are all those threads for the same process rather than separate processes? I have a Tomcat 4.x server running on a Linux 2.4.x kernel and see the same thing.

You probably know this, but just in case: you can cap the memory a JVM uses with command-line arguments: -Xms=xxxM sets the initial heap size (in MB), -Xmx=xxxM sets the max. (More with 'java -X -?'.) With tomcat these are typically set in your bin/catalina.sh file using JAVA_OPTS from the environment.
- Re:not that java ain't a pig... (Score:2)
  
  by Matts (1087)
  
  But capping the memory usage doesn't make it use less memory does it? I thought it just made it run OUT of memory sooner.
  - Re:not that java ain't a pig... (Score:2)
    
    by lachoy (1663) <chris.winters@gmail.com> on 2005.06.13 12:51 (#41112) Homepage Journal
    
    Yep, capping the memory usage just means it won't eat up all the memory (and swap) of your machine, which seemed to be the complaint. I think that once you hit the limit you'll just start getting java.lang.OutOfMemoryError exceptions.
    
    Reply to This
    
    Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.