On 2004.08.19, Jim Wilcoxson <[EMAIL PROTECTED]> wrote: > For fastpath (static file serving), reading a file into a memory > buffer would seem to scale well for typical web size images: 250K or > less, especially considering that fastpath already uses a memory > cache. I can see 3 scenarios: > > 1. File is small: put it in the cache, leave it there after spooling > 2. File exceeds cache size limit, but is less than 1MB: put it in the > cache, delete it after spooling or make it expire "very soon" > 3. File is huge: let the connection thread spool it, like it does now, > and don't spool it, or
The Netscape Enterprise Server (NES) web server has a static file cache that's tunable ... "nfsc" rings a bell. You specify things like the max number of entries in the cache, the byte size ranges that define "small", "medium" and "large" files, etc. Could be an interesting idea to accelerate fastpath static content serving from AOLserver. Maybe. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
