On Tue, 20 May 2008, MA QING A wrote:The test I used is a performance test, not a latency test. An RTOS (Real-time Operating System) will sacrifice performance to achieve determinism (low latencies). Several key features to an RT system usually come with a performance cost. A non RT system will perform 99% of the time faster than an RTOS. But all it takes is that one time to miss a deadline to make an RT system crash. An RTOS may be slightly slower, but it will not have those outliers that a normal desktop system would have. So getting back to your question. Hackbench runs a bunch of stuff and times how long it took to do so. It stresses the system quite a bit. The lower the number the better. Given that hackbench is not checking for latency, but only shear perforance, it is expected that hackbench will run better on a non RT system. Now, a test like cyclictest that measures latencies will show the benefits of realtime. The kernel with the RT patch can measure 65 microsecond latencies for response times even while running hackbench. The vanilla kernel would measure a few milliseconds response times running the same test. -- Steve --
| Mike Galbraith | Re: regression: CD burning (k3b) went broke |
| Andi Kleen | [PATCH] [3/22] x86_64: Kill temp boot pmds |
| Alan Cox | Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...? |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 05/37] dccp: Cleanup routines for feature negotiation |
| Brandeburg, Jesse | RE: [PATCH] e1000e: test MSI interrupts |
