use Perl

• 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)

      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.
• Conspiracy theories (Score:1)

  by mary.poppins (3530)

  As I wrote in my profile:
  
  My personal theory is that Java is a fraud perpetrated by Sun to stimulate hardware sales. "What? Too slow? Tends to eat up all of swap? You obviously need our new E20599000!"
• threads (Score:1)

  by sky (1411)

  Top is being stupid and showing all threads, press H and it shows you a better view of the world.... as I pointed out earlier today.
  
  The reason that machine is slow is because it starts swaping programs to it's local IDE disk to get more buffer space reading from a SAN that has 8GB of read cache, and the ide causes interrupt storms and the machines start crawling..
  
  Linux in it's infinitly stupid swap implementation.

  --
  sky