public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com, andrea@suse.de, axboe@suse.de
Subject: as vs cfq vs deadline
Date: Mon, 24 Feb 2003 00:49:24 +0800	[thread overview]
Message-ID: <20030223164924.16952.qmail@linuxmail.org> (raw)

Hi all,
I've run a 'let's check if it does not skip frames test'.
kernel is 2.5.62-mm2.

** How I performed the test **
startx
I've opened to xterminal

terminal1
[test@frodo test]$ glxgears

terminal2
./dbench 16

Following the results:

** booted with scheduler=as ** 
Throughput 19.8092 MB/sec (NB=24.7615 MB/sec  198.092 MBit/sec)  16 procs

[test@frodo test]$ glxgears
609 frames in 5.0 seconds = 121.800 FPS
673 frames in 5.0 seconds = 134.600 FPS
676 frames in 5.0 seconds = 135.200 FPS
591 frames in 5.0 seconds = 118.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
592 frames in 5.0 seconds = 118.400 FPS
-- Here dbench starts --
591 frames in 7.0 seconds = 84.429 FPS
423 frames in 5.0 seconds = 84.600 FPS
422 frames in 5.0 seconds = 84.400 FPS
507 frames in 5.0 seconds = 101.400 FPS
602 frames in 5.0 seconds = 120.400 FPS
676 frames in 5.0 seconds = 135.200 FPS
591 frames in 5.0 seconds = 118.200 FPS
592 frames in 5.0 seconds = 118.400 FPS
422 frames in 9.0 seconds = 46.889 FPS
423 frames in 5.0 seconds = 84.600 FPS
507 frames in 5.0 seconds = 101.400 FPS
507 frames in 5.0 seconds = 101.400 FPS
507 frames in 5.0 seconds = 101.400 FPS
422 frames in 5.0 seconds = 84.400 FPS
338 frames in 5.0 seconds = 67.600 FPS
254 frames in 7.0 seconds = 36.286 FPS
338 frames in 8.0 seconds = 42.250 FPS
507 frames in 10.0 seconds = 50.700 FPS
84 frames in 5.0 seconds = 16.800 FPS
-- dbench stops here --
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
X connection to :0.0 broken (explicit kill or server shutdown).



** booted with scheduler=cfq **
Throughput 24.3661 MB/sec (NB=30.4577 MB/sec  243.661 MBit/sec)  16 procs

[test@frodo test]$ glxgears
689 frames in 5.0 seconds = 137.800 FPS
675 frames in 5.0 seconds = 135.000 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
591 frames in 5.0 seconds = 118.200 FPS
-- dbench starts here --
507 frames in 5.0 seconds = 101.400 FPS
338 frames in 5.0 seconds = 67.600 FPS
507 frames in 5.0 seconds = 101.400 FPS
616 frames in 5.0 seconds = 123.200 FPS
507 frames in 5.0 seconds = 101.400 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
591 frames in 5.0 seconds = 118.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
423 frames in 6.0 seconds = 70.500 FPS
338 frames in 8.0 seconds = 42.250 FPS
422 frames in 5.0 seconds = 84.400 FPS
169 frames in 7.0 seconds = 24.143 FPS
507 frames in 16.0 seconds = 31.688 FPS
338 frames in 5.0 seconds = 67.600 FPS
-- dbench stops here --
676 frames in 5.0 seconds = 135.200 FPS
592 frames in 5.0 seconds = 118.400 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
X connection to :0.0 broken (explicit kill or server shutdown). 


** booted with scheduler=deadline **
Throughput 28.7021 MB/sec (NB=35.8776 MB/sec  287.021 MBit/sec)  16 procs

[test@frodo test]$ glxgears
687 frames in 5.0 seconds = 137.400 FPS
589 frames in 5.0 seconds = 117.800 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
-- dbench starts here --
423 frames in 5.0 seconds = 84.600 FPS
591 frames in 5.0 seconds = 118.200 FPS
676 frames in 5.0 seconds = 135.200 FPS
338 frames in 5.0 seconds = 67.600 FPS
507 frames in 5.0 seconds = 101.400 FPS
676 frames in 5.0 seconds = 135.200 FPS
592 frames in 5.0 seconds = 118.400 FPS
338 frames in 5.0 seconds = 67.600 FPS
253 frames in 9.0 seconds = 28.111 FPS
169 frames in 7.0 seconds = 24.143 FPS
507 frames in 15.0 seconds = 33.800 FPS
169 frames in 5.0 seconds = 33.800 FPS
-- dbench stops here --
676 frames in 5.0 seconds = 135.200 FPS
676 frames in 5.0 seconds = 135.200 FPS

I can not see any difference in the results above.

I guess the test I've run it is not a good test, isn't it ?

Comments/suggesiontions ?

Ciao,
		Paolo
		
-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-02-23 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-23 16:49 Paolo Ciarrocchi [this message]
2003-02-25 22:42 ` as vs cfq vs deadline Kevin Puetz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030223164924.16952.qmail@linuxmail.org \
    --to=ciarrocchi@linuxmail.org \
    --cc=akpm@digeo.com \
    --cc=andrea@suse.de \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox