Linked by Thom Holwerda on Sun 7th May 2006 14:05 UTC, submitted by Mystilleef
Thread beginning with comment 122331
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-01-14
I agree that some portions of the Mac OS X kernel need optimizations but:
- If I could get a nice statistical software that runs fine under Mac OS X and plays well with other software I use AND the workflow under Mac OS X would safe MY time (and I suppose it would) I would run that software under Mac OS X and not under Linux to save some cpu cycles.
- I also run some file / directory servers under Mac OS X because integrating Mac / Win / Linux works for me really well (and nobody complaned about performance so far)
- I also think that the statistical software package may have been tweaked (over time) for Linux perfomance - Mac OS X is not Linux and that does not means that it is slower but that it has a different performance profile.
There is an article on Apples developer pages how to optimize MySQL performance by turning off a MySQL feature that dynamically changes thread priority - the very same feature that increases performance under Linux.
- This is not to say that Apple should not optimize the kernel that has 16 year old code in it (Apple has allready done this successfully with launchd) - but this article draws just the wrong conclusions.