Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 530 invoked by uid 6000); 4 Nov 1998 05:56:53 -0000 Received: (qmail 522 invoked from network); 4 Nov 1998 05:56:51 -0000 Received: from proxy4.ba.best.com (root@206.184.139.15) by taz.hyperreal.org with SMTP; 4 Nov 1998 05:56:51 -0000 Received: from mdaxke (mg134-013.ricochet.net [204.179.134.13]) by proxy4.ba.best.com (8.9.0/8.9.0/best.out) with SMTP id VAA24601; Tue, 3 Nov 1998 21:53:37 -0800 (PST) Message-ID: <071601be07b6$c5f8c5d0$0200a8c0@mdaxke.mediacity.com> From: "Mark D. Anderson" To: , "Dean Gaudet" Subject: Re: Apache 2.0 ideas Date: Tue, 3 Nov 1998 21:48:35 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On a related note, if there is a choice of methods (e.g. sendfile vs. memory), could the web server just try them both on successive requests and in the future (on that resource), pick the faster? There would have to be adjustment for hotness of the caches, but you get the idea. That would relieve people of tuning their system manually. I really have no idea how big a "big" file is, and I'm sure the answer changes from OS/arch to another -- and even on one OS/arch will vary with available RAM. -mda