Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 22490 invoked by uid 6000); 21 Nov 1997 02:32:25 -0000 Received: (qmail 22481 invoked from network); 21 Nov 1997 02:32:23 -0000 Received: from localhost.hyperreal.org (HELO brianb.organic.com) (127.0.0.1) by localhost.hyperreal.org with SMTP; 21 Nov 1997 02:32:23 -0000 Message-Id: <3.0.3.32.19971120182715.009a8380@localhost> X-Sender: brian@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 20 Nov 1997 18:27:15 -0800 To: new-httpd@apache.org From: Brian Behlendorf Subject: Re: Want to add file caching to Apache Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >From a contact at Microsoft: >If you do add file caching to apache, make sure to leave a way not to do >this on NT. File caching comes for free when you use the Win32 functions >like TransmitFile, etc that we have talked about using for Apache 2.0. To >manage the file cache you setup a file handle cache, closing file handles >when you do not need the file in cache and keeping open the ones you do want >in cache. Implementing a separate file cache would move the file cache out >of the kernel into user space and would force copies of the file date, which >is very CPU expensive... > >The implementation below is sometimes called file shadowing, Netscape >implements it (I think). What we have seen is that this adds about 5% >performance increase when all data can fit into RAM, and about a 40% >performance penalty (at least on NT, don't know about other OSes) when there >is more active data than RAM, because it requires extra file copies, etc. --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- "it's a big world, with lots of records to play." - sig brian@organic.com