AFAIK, the memory is shared among threads, no matter whether system or
ruby’s.
The memory for the whole ruby process/script is allocated on demand,
with some initial amount.
This amount and growing ratio is compiled-in (at least for 1.8).
AFAIK, the memory is shared among threads, no matter whether system or ruby’s.
Exactly. That’s the whole point of threads.
The memory for the whole ruby process/script is allocated on demand,
with some initial amount.
This amount and growing ratio is compiled-in (at least for 1.8).
And there is no way to limit it. It might be possible to limit on a per
process base (depending on OS, see “ulimit -a”) but not on a per thread
base. And there might be a limit on the stack size. But it does not
make sense to limit memory allocated by a thread because the memory is
shared and can be used from any thread.
The memory for the whole ruby process/script is allocated on demand,
And there is no way to limit it. It might be possible to limit on a per
Pokkai, what’s your primary goal/problem? Why do you want to limit the
memory?
Maybe there’s a solution if you can look at the problem from another
angle.
J.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.