W. Chris Shank on Thu, 8 Aug 2002 09:20:27 -0400 |
i agree with these guys too. anything you do in java is going to be ram intensive. limiting the memory heap is a good idaa and will keep java resources low, but will slow your jvm even more. also, you can try green-threads instead of native threads. - don't recall exactly what the switch is for threading, maybe -Dthreads=green. a quick google search should find it. but your best bet is to get more ram and/or a faster box. > On Thu, Aug 08, 2002 at 01:37:34AM -0400, Mental Patient wrote: >> Keith Bentrup wrote: >> >Hi everyone, >> > I am running tomcat4 on my RH7.2 box. It's an old box and >> >doesn't have much memory, so I am trying to limit the number of >> >processes it loads. I specify maxProcessors of 5 in the server.xml, >> >but when I do ps, it shows 20 running. Anyone know what gives? >> >Tomcat is really bogging down my machine. Help will be greatly >> >appreciated. Thanks, >> >> Threads show up as processes in linux. >> >> >> Why on earth would you run java on a low memory machine? Its going to >> suck. If its educational for you to learn in or something, set >> maxprocesses to 1 or something and maybe you'll be ok. >> > Agreed. > > Depending on which JVM you are using, the -Xmx switch could be > available which limits the size of the memory pool used. > _________________________________________________________________________ > Philadelphia Linux Users Group -- > http://www.phillylinux.org Announcements - > http://lists.netisland.net/mailman/listinfo/plug-announce General > Discussion -- http://lists.netisland.net/mailman/listinfo/plug _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|