Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 30 Aug 2002 13:18:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 30 Aug 2002 13:18:27 -0400 Received: from e2.ny.us.ibm.com ([32.97.182.102]:25240 "EHLO e2.ny.us.ibm.com") by vger.kernel.org with ESMTP id ; Fri, 30 Aug 2002 13:18:26 -0400 Date: Fri, 30 Aug 2002 10:19:15 -0700 From: "Martin J. Bligh" To: Roy Sigurd Karlsbakk , Andrew Morton cc: linux-kernel@vger.kernel.org Subject: Re: [BUG+FIX] 2.4 buggercache sucks Message-ID: <30940000.1030727954@flay> In-Reply-To: <200208301121.06437.roy@karlsbakk.net> References: <200208291000.46618.roy@karlsbakk.net> <318656043.1030603363@[10.10.2.3]> <200208301121.06437.roy@karlsbakk.net> X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 916 Lines: 19 >> Was your workload doing lots of reads, or lots of writes? Or both? > > I was downloading large files @ ~ 4Mbps from 20-50 clients - filesize ~3GB > the box has 1GB memory minus (no highmem) - so - 900 megs. After some time it > starts swapping and it OOMs. Same happens with several userspace httpd's Mmmm .... not quite sure which way round to read that. Presumably the box that was the server fell over, and the clients are fine? So the workload that's causing problems is doing predominantly reads? If so, I suggest you tear down Andrew's patch to read side only, and submit that ... I get the feeling that would be acceptable, and would solve your problem. M. - 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/