public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Jeff Garzik <jgarzik@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9: performance issues on Via Epia
Date: Wed, 20 Oct 2004 01:17:29 +0100	[thread overview]
Message-ID: <200410200117.29871.alistair@devzero.co.uk> (raw)
In-Reply-To: <200410192346.14695.vda@port.imtp.ilyichevsk.odessa.ua>

On Tuesday 19 Oct 2004 21:46, you wrote:
> On Tuesday 19 October 2004 18:04, Alistair John Strachan wrote:
> > Hi,
> >
> > I recently upgraded from 2.6.8.1 to 2.6.9 (the release, not -final) on my
> > Via Epia 5000 router. Now when I transfer files from the machine's HD
> > vsftpd can only achieve 3MB/s.
> >
> > I believe this is some performance problem specifically related to XFS,
> > or something specific to the local VM, because if I transfer from an NFS
> > mounted directory on the same machine, vsftpd easily achieves the 10MB/s
> > I'm used to.
>
> Sound like 'DMA off' problem.

Could be, not changed anything since 2.6.8.1 though and dmesg claims dma is 
enabled on hda, which is the only connected drive

>
> > Top shows something typical to this during transfers from the machine's
> > local HD;
> >
> > Cpu(s):  0.7% us,  9.2% sy,  0.0% ni,  0.3% id, 84.5% wa,  5.3% hi,  0.0%
> > si
> >
> > Which seems like an awful lot of wait time. Anybody got any suggestions
> > of where to start reverting patches? The amount of difference between
> > 2.6.8.1 and 2.6.9 is quite daunting.
>
> Binary search is converging quickly.

That's still a lot of work, but thanks.. I'll probably just work through the 
bk snapshots until it breaks, then binary search on the remaining patches. 
It'll still take a couple of hours, especially on such a slow machine.

>
> > By the way, copying a file locally on the system from the same partition
> > to another directory is far more efficient.
> >
> > [root] 16:02 [~] time cp /var/cache/swapfile here
> > `/var/cache/swapfile' -> `here'
> >
> > real    0m37.904s
> > user    0m0.115s
> > sys     0m13.033s
>
> size of this file?

512MB, sorry about that..

By the way Jeff, I already said in my original post that copying from a local 
NFS mount gives me to get the full 10MB/s i.e.

NFS server X -> problem case machine's NFS mount -> some client machine = fine
problem case machine's local mount -> some client machine = slow.

My email was just an attempt to stir up any obvious changes that might've 
taken place. Since the problem seems obscure, I'll probably have to do it 
properly and manually search through the patches until I find the problem 
one.

Thanks for your prompt replies.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.

      reply	other threads:[~2004-10-20  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 15:04 2.6.9: performance issues on Via Epia Alistair John Strachan
2004-10-19 16:38 ` Jeff Garzik
2004-10-19 20:46 ` Denis Vlasenko
2004-10-20  0:17   ` Alistair John Strachan [this message]

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=200410200117.29871.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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