lkml.org 
[lkml]   [2002]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [BUG] 2.4 VM sucks. Again
Date
> I suspect nuke-buffers is simply always the right thing to do.  It's
> what 2.5 is doing now (effectively). We'll see...
>
> But in your case, you only have a couple of gigs of memory, iirc.
> You shouldn't be running into catastrophic buffer_head congestion.
> Something odd is happening.
>
> If you can provide a really detailed set of steps which can be
> used by others to reproduce this, that would really help.

What I do: start lots (10-50) downloads, each with a speed of 4,5Mbps from
another client. The two are connected using gigEthernet. downloads are over
HTTP, with Tux or other servers (have tried several). If the clients are
reading at full speed (e.g. only a few clients, or reading directly from
localhost), the problem doesn't occir. However, when reading at a fixed rate,
it seems like the server is caching itself to death.


Detailed configuration:

- 4 IBM 40gig disks in RAID-0. chunk size 1MB
- 1 x athlon 1GHz
- 1GB RAM - no highmem (900 meg)
- kernel 2.4.19pre7 + patch from Andrew Morton to ditch buffers early
(thread: [BUG] 2.4 VM sucks. Again)
- gigEthernet between test client and server

Anyone got a clue?

--
Roy Sigurd Karlsbakk, Datavaktmester

Computers are like air conditioners.
They stop working when you open Windows.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.109 / U:1.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site