On Fri, 15 Mar 2002 09:47:14 -0500 Bill Davidson <[EMAIL PROTECTED]> wrote:
> Now I'm curious. How did you find that out? I looked into /proc/sys/kernel/threads-max the number was 3063 (I hadn't set anything here and was curious so this is a stock number) Then since my ram was larger and the stock number was larger I divided 3063 by 384 and came up with (rounded) 7.98 when I did 1024 divided by 128 I got 8 so I assumed (lousy idea but I did it anyway) that the ratio is around 8 x ram = number in /proc/sys/kernel/threads-max. James > > Bill > > On Friday 15 March 2002 03:49 am, James wrote: > > Raffaele, > > Your letter is one of those that peeks curiosity. I looked at my box > > (running 384 megs) and found that the number was 3063 you said you had > > 128 megs and 1024 ... The ratio seems to be about 8xram in megs .... > > don't know what this means or why it's set to this but maybe this will > > help. > > > > James > > > > > > On Fri, 15 Mar 2002 08:52:14 +0100 > > > > Raffaele Belardi <[EMAIL PROTECTED]> wrote: > > > I had problems running a fairly big applet in the Forte for Java 3.0 > > > with JSDK 1.3.1: the IDE started ok, but when I tried to execute the > > > applet I got an "out of memory" error (on a 128Mbyte machine). > > > > > > I found out that for some reason the threads-max kernel tunable was > > > set to 1024, which turns out to be too small for the IDE. [is this a > > > default for MDK 8.1, or was it changed when I played with the security > > > things?] > > > > > > Changing to 32K with > > > # echo 32768 > /proc/sys/kernel/threads-max > > > fixed the issue. > > > > > > bye, > > > > > > raffaele - italy > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
