Linked by Thom Holwerda on Thu 3rd May 2012 21:26 UTC, submitted by PhilJ
Thread beginning with comment 517048
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2007-01-18
Often, when you install a critical 3rd-party package (e.g. a memory hog one), you'll see some instructions on how to deal with it. In most cases, an
$ ulimit -d 1048576
will solve your problem.
As explained by 0brad0, OpenBSD uses a different allocator, more restrictive, that doesn't allow crap software.
What I have seen so far, and strangely enough, are that users who recompile kernels to cut some MBs are the ones who generally have GBs of memory. In the same line, users who complain about speed _generally_ have multi-GHz CPUs. Is this the case?