ten thousand small processes

Petri Helenius pete at he.iki.fi
Thu Jun 26 14:51:54 PDT 2003

> Funny. Seems to me that I keep making concrete suggestions---including a
> detailed proposal for giving more space to malloc()---and the answer is
> consistently ``We really don't care about per-process overhead.'' What's
> the benefit of a patch for people who don't even see the problem?
Many programmers read and write C more fluently than they do english.

Code can also be run trough the common case benchmarks, proving that
the improvements you suggest are not going to detoriate the 99.9%++
of users who don´t have 10000 processes.

In general, not to dismiss the requirements, I think the design is broken
if you require permission separation and memory separation between
10000 processes which run identical code, since that implies that either
the code is badly designed, horribly broken or you expect it to be either
or both. The only viable option would be that part of the executable actually
comes somewhere else which kind of dismisses the optimization parameters
because then the size would be unknown.

Memory is cheap and FreeBSD supports 64G of it.


More information about the freebsd-performance mailing list