All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jens Benecke <mail-020509@jensbenecke.de>
Cc: ReiserFS Mailingliste <reiserfs-list@namesys.com>,
	zam@thebsh.namesys.com
Subject: Re: Improved performance by reformatting?
Date: Fri, 10 May 2002 05:33:01 +0400	[thread overview]
Message-ID: <3CDB234D.4030700@namesys.com> (raw)
In-Reply-To: 20020509234806.GA4635@jensbenecke.de

Jens Benecke wrote:

>Hi,
>
>recently I have begun to notice that my server (Duron 650, Via chipset,
>UDMA harddisks, hdparm says 30-35MB/sec on the raw device) have been
>slowing down during long copy actions. If I copy a 300MB file, e.g.
>midnight commander pauses frequently, sometimes over ten seconds, while
>the CPU Load (according to xosview) is stuck at 100%.
>
>DMA and so on is enabled on all harddisks.
>
>The file systems in question were created with early 2.4 kernels (2.4.4
>IIRC) and one of them is a LVM volume which was resized and moved
>several times until now. Would a backup & reformat & restore noticeably
>improve performance to make it worth the effort?
>
>I'm asking this because I will have the chance to do this shortly (new
>harddisks) and if it will make a difference, I will not just copy the
>stuff over, but recreate the FS.
>
>
>  
>
You need the latest bitmap.c (ask zam), and to turn off border, and turn 
on skip_busy.

If I can just get some decent benchmarks, we'll determine what options 
should be standard, and put this bitmap.c in the mainline kernel, but 
there are delays in benchmarking....

Hans



       reply	other threads:[~2002-05-10  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020509234806.GA4635@jensbenecke.de>
2002-05-10  1:33 ` Hans Reiser [this message]
2002-05-10  1:35 ` Improved performance by reformatting? Hans Reiser

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=3CDB234D.4030700@namesys.com \
    --to=reiser@namesys.com \
    --cc=mail-020509@jensbenecke.de \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@thebsh.namesys.com \
    /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.