Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934368AbXEVO3v (ORCPT ); Tue, 22 May 2007 10:29:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757490AbXEVO3o (ORCPT ); Tue, 22 May 2007 10:29:44 -0400 Received: from pool-72-92-171-78.albyny.east.verizon.net ([72.92.171.78]:50193 "EHLO posidon.tmr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758169AbXEVO3o (ORCPT ); Tue, 22 May 2007 10:29:44 -0400 Message-ID: <4652FDEF.8060209@tmr.com> Date: Tue, 22 May 2007 10:27:59 -0400 From: Bill Davidsen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: Linux Kernel M/L CC: Ingo Molnar , Con Kolivas , Linus Torvalds Subject: Scheduler smoothness and fairness - results and package Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1791 Lines: 38 Thanks to the suggestions of several people and some encouragement, I've done another upgrade of the schedular characteristic package glitch1. For "bottom line" folks, the results are at http://www.tmr.com/~davidsen/sched_smooth_03.html This package runs four fast scrolling xterms and a copy of glxgears to produce both screen update and CPU load. In addition to the human observation of smoothness, the glxgears speeds are characterized by variance from sample to sample, and the number of random numbers generated by the xterm programs are also characterized. Changes: - Reruns for a given configuration are shown in a single row. - The analysis has had minor output format and statistical tweaks for correctness as well as handling of multiple run output in a single row. - the glxgears 1st value is shown as a separate item, since there is a large stoppage on the first sample after cold boot with some schedulers. The full source and doc is now available from http://www.tmr.com/~public/source/ so people can do their own runs. Note that values between different machines are almost certainly not meaningful. Having run all this on a dual core Core2duo in x86 (32 bit) mode, I'm now off to rerun in x86_64 mode, and on a single CPU hyperthreaded machine, and a pure uniprocessor. I'm going to create a page for all the results in one place for anyone who cares. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/