Linked by Thom Holwerda on Thu 3rd May 2012 21:26 UTC, submitted by PhilJ
Thread beginning with comment 516989
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.
"That's not really an OpenBSD problem but a problem with the app. Quite a few "portable" programs a written with the mentality that if it works on Linux that's good enough.
That is one of the greatest problems with generally open source world. It usually takes care about Linux, everything else seems to be forgotten.
I only use OpenBSD in infrastructure roles though so maybe this is a problem more noticed on the desktop.
There is a noticeable slowdown on the "desktop". I suspect the main culprits are a) userthreads and b) malloc.
a) Using userthreads means a huge multithreaded program is running on a single cpu core wasting all the threading overhead.
b) OpenBSD malloc is pretty complex and has many features - most importantly ASLR which consumes high quality random numbers on a regular basis. There is no way it could outperform a decent performance-optimized malloc. Huge multithreaded programs tend to allocate and deallocate thousands of objects every millisecond so it ends up adding up.
On the command line, most programs a) use SMP-enabled processes instead of threads and b) are written in C which means all allocations are planned. It is perfectly possible they could outperform an out of the box Linux with many daemons half-idling in the background.
I certainly don't have any complaint about make -j 6 in /GENERIC.MP.
OpenBSD 5.2 will include SMP-enabled rthreads by default so I expect to see a boost in "desktop" performance. malloc is less likely to improve but memmap is getting reworked, which could lead to a faster implementation.
NOTE: The network stack runs in kernel and thus it won't scale over 1 core until the kernel itself becomes multithreaded.




Member since:
2005-08-18
True but I can't even remember the last time I used that. If there's not a native port the program probably wouldn't run very well in Linux emulation anyway.
Yes, I have heard that localization is somewhat incomplete in the base system. For GUI apps not in base it is not an OpenBSD problem.
Don't bother me much though, English is the language of computers. Just deal with it or contribute what is necessary to improve localization.
That's not really an OpenBSD problem but a problem with the app. Quite a few "portable" programs a written with the mentality that if it works on Linux that's good enough.
Maybe but I haven't noticed any real difference between, for example, OpenBSD and Linux. If anything OpenBSD feels faster.
I only use OpenBSD in infrastructure roles though so maybe this is a problem more noticed on the desktop.
On an unrelated note, I think this should be front page news on *OS*news.
Edited 2012-05-04 03:51 UTC