All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@norran.net>
To: linux-mm@kvack.org
Subject: mmap002 execution time doubled... good or bad sign?
Date: Sat, 10 Feb 2001 23:23:19 +0100	[thread overview]
Message-ID: <01021023231906.02374@dox> (raw)

Hi,

I have been running various stress tests on disk for some time.
streaming write, copy, read, diff, dbench and mmap002

This is what I have seen:

>From 2.4.0 to 2.4.1 with Marcelos patch write were above 10 MB/s
and read >13 MB/s, dbench > 10 MB/s, mmap took around 2m30.

After 2.4.1-pre8 (did not test anything in between)
Write is at 9-10 [lost 1 MB/s] read is down to 11-12 MB/s [lost 2 MB/s]
dbench > 9 MB/s [one MB/s there too]

But the really strange one - mmap002 now takes > 4m30
Is this expected / good behaviour? mmap002 abuses mmaps...

/RogerL

-- 
Home page:
  none currently
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2001-02-10 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 22:23 Roger Larsson [this message]
2001-02-11  2:05 ` mmap002 execution time doubled... good or bad sign? Marcelo Tosatti

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=01021023231906.02374@dox \
    --to=roger.larsson@norran.net \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.