>Number: 2669 >Category: general >Synopsis: Files being served are loaded into memory then served >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Jul 22 17:00:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.0 >Environment: FreeBSD 3.0-980509-SNAP >Description: at MP3.COM we use Apache to serve MP3 downloads (legal :) via http as opposed to ftp. The problem is that a lot of people have slow connections, and Apache appears to load the entire file being served into memory, creating a lot of copies of Apache which are each very large... at one point I had over 100 instances of Apache running, consuming about 400 MB of RAM, all to serve up about 4 Mb/s of data... >How-To-Repeat:
>Fix: I understand that you want to load the file initially for speed and simplicity reasons, and it's the "correct" solution, but for us http is a much nicer download solution than ftp, and it would be nice to say something like: MaxFilePreloadSize 100K Or somesuch, so large files aren't loaded into memory to sit around for an hour while someone with a 28.8 modem downloads them. I searched around and maybe I missed something, but I couldn't find anything relevant to this. On a side note, I think mod_throttle or mod_bandwidth or a combination of both should be included in Apache by default... they are extremely useful for our situation! >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
