Emmanuel Florac wrote:Unfortunately this shows the same trend as kernel compile, small database operations, etc. If you are using a journaling filesystem on 2.6 and not 2.4 be sure you have the filesystem mounted "noatime" or retest with a non-journaled f/s. If you are running LVM in the test all bets are off as there are alignment issues (see linux-raid archives) to consider. But the trend has unfortunately been slower, and responses demanding you use another benchmark, saying that kernel compile is not a benchmark, suggesting use of postgress or oracle instead of MySQL, etc, are seen. I wish it were not so, there seems to be more effort going to explaining results than improving them. That said, tuning the location of the f/s, the stride, chunk size, etc, can improve things, and there are patches available for test (linux-raid again) which will address some of this fairly soon. -- Bill Davidsen <davidsen@tmr.com> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot --
| James Bruce | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Peter Zijlstra | [RFC/PATCH 0/4] CPUSET driven CPU isolation |
git: | |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Rick Jones | Re: Network latency regressions from 2.6.22 to 2.6.29 |
| David Miller | [GIT]: Networking |
| Josip Rodin | bnx2_poll panicking kernel |
