From: brian@worldcontrol.com
To: Christiaan Kok <chrkok@chem.rug.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.17 gets really slow when handling large files
Date: Fri, 11 Jan 2002 13:56:50 -0800 [thread overview]
Message-ID: <20020111215650.GA2943@top.worldcontrol.com> (raw)
In-Reply-To: <m16OyYV-000t5oC@polypc17.chem.rug.nl>
In-Reply-To: <m16OyYV-000t5oC@polypc17.chem.rug.nl>
On Fri, Jan 11, 2002 at 11:04:59AM +0100, Christiaan Kok wrote:
> Dear people,
>
> I have a problem with kernel 2.4.17 and as far as I have testen all the 2.4.X
> kernels before it. When handling large files, like moving or viewing movies
> (700 Mb) (with mplayer) my system suddenly slows down a lot. This can only be
> repaired by a reboot. hdparm -Tt /dev/hdX values drop from around 25 MB/s to
> around 8 MB/s but DMA is still on (at least that is what hdaprm reports). In
> is a such a state it is imposible to burn cds for instance but networkspeed is
> unharmed.
How slow? Does it always happen when playing large files with mplayer
or only some of the time?
I've run into a similar sounding problem.
Running mplayer, sometimes, perhaps 1 to 50 runs, the system becomes
nearly unresponsive. I can switch virtual desktops in X, via WM,
promptly. Through redraws of the switched-to desktop are slow.
xmms playing music continues to play fine.
rxvt's have about a 4 second response time.
Generally, I can manage rebooting the laptop.
Originally I blamed low-latency patches, and have switch back to
2.4.17 with preempt-patch.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
next prev parent reply other threads:[~2002-01-11 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 10:04 Kernel 2.4.17 gets really slow when handling large files Christiaan Kok
2002-01-11 13:03 ` Alan Cox
2002-01-11 21:56 ` brian [this message]
2002-01-11 22:06 ` Timothy Covell
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=20020111215650.GA2943@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=chrkok@chem.rug.nl \
--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 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.