Linked by evilsjg on Wed 16th Nov 2011 00:17 UTC
Permalink for comment 497380
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-03-29
These benchmarks were not exhaustive or totally scientific, nor were they intended to be. Your issues with the methodology does not invalidate the fact that these benchmarks convey relative performance for this test with reasonable accuracy.
DragonFly has a more invasive INVARIANTS than FreeBSD, we leave it enabled for releases and feel that the FreeBSD policy of disabling it is a mistake. Bugs and crashes happen and when they happen to our users in a production environment using a release not having INVARIANTS limits their ability to properly report a bug as well as our ability to pinpoint and fix the problem. That is the stance of the project and the rationale for that stance, but if someone wanted to test both without INVARIANTS, I am relatively sure DragonFly would see a larger bump.