9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alberto Nava beto@plan9.cs.su.oz.au
Subject: yet another benchmark
Date: Fri, 18 Nov 1994 14:10:41 -0500	[thread overview]
Message-ID: <19941118191041.buOLrSqML2l-H4-MGioJ3V6r74-AKqYh33g8slMz3XQ@z> (raw)

In <94Nov17.000230est.12684@galapagos.cse.psu.edu>
	Scott Schwartz <schwartz@galapagos.cse.psu.edu> wrote:

> Larry McVoy posted a filesystem benchmark on comp.unix.bsd today,
> Message-ID: <3ae05t$afs@fido.asd.sgi.com>.  I'm not sure what it's
> intended to prove, but since I'm a sucker for benchmarks I ran it
> anyway. :-)
> 
> Here are the results and the code (tweaked to compile).  Maybe someone
> with more interesting hardware than an SS1 cpu server and SS2 file
> server can share their results.  
> 
> cpu% k.out
> 0k	500	36	63
> 1k	500	19	50
> 4k	500	15	56
> 10k	500	11	56
> cpu% ramfs
> cpu% cd /tmp
> cpu% $home/k.out
> 0k	500	42	100
> 1k	500	36	100
> 4k	500	28	125
> 10k	500	11	17
> 
> 

We don't have a great hardware, but we are my results.

#
# terminal: SPARC ELC 
# file server: Sparc ELC
# cpu server: Sparc ELC
#

term% k.out
0k	500	26	45
1k	500	13	38
4k	500	11	29
10k	500	8	26

cpu% k.out
0k	500	26	63
1k	500	13	38
4k	500	12	28
10k	500	10	28

#
# with ramfs
#

term% $home/src/ben/k.out
0k	500	56	125
1k	500	50	100
4k	500	42	125
10k	500	9	24	

cpu% $home/src/ben/k.out 
0k	500	63	167			  
1k	500	56	125
4k	500	42	167
10k	500	28	167

The result for our cpu server running ramfs are a little better. Probably
becuase it has more RAM. 






             reply	other threads:[~1994-11-18 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-18 19:10 Alberto [this message]
  -- strict thread matches above, loose matches on Subject: below --
1994-11-17  6:29 Scott
1994-11-17  5:02 Scott

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=19941118191041.buOLrSqML2l-H4-MGioJ3V6r74-AKqYh33g8slMz3XQ@z \
    --to=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).