I am not sure this is the best place to post this question, but I am having a very hard time geting over this issue. I am creating a download proxy to secure file downloads from our web site. I have written some code that *could* do this if I had a way to determine
the size of IIS's output buffer. In a nutshell I have several 500mb files that logged in users have access to... and 30 logged in users. If I were to use response.writefile this would require about 15Gb of memory in the server. What I have so far is I disable
the output buffer, read in the first 10kb of the file, write that to the response object (outputstream written with a binarywriter), flush that data and wait a short while. I then grab the next 10k or so and repeat the process. This method is not in tune with
the actual rate at which the file data is sent to the clients so it is possible to either run out of memory by sending too much data at a time, or making the client wait unnecessarily by not sending the data fast enough. I know this might be a bit foggy, but
I can provide code to anyone with any ideas. Any help would be greatly appreciated!
Try this hotfix and use new TransmitFile method: http://support.microsoft.com/default.aspx?kbid=823409 "FIX: Downloading Large Files Causes a Large Memory Loss and Causes the Aspnet_wp.exe Process to Recycle". Hope this helps! Maria
None
0 Points
5 Posts
Download large files runs out of memory (IE: response.writefile)
Jun 08, 2004 08:03 PM|asp949|LINK
None
0 Points
46 Posts
Re: Download large files runs out of memory (IE: response.writefile)
Jun 23, 2004 02:51 PM|MariaTv|LINK