S
Steven Bazeley
I had a download failure problem with a 95MB wmv file. I thought it was my
code
but I could not find anything wrong. So I tested the download by replacing
the 95MB
file with a smaller one (20MB). It worked fine. When I contacted my hosting
company
this is what they told me.
(Data streamed through the Response buffer will be held in memory. We allow
a maximum of 100MB memory usage per site.
The 100MB memory limit is applied to the site's application process. Your
site itself is using about 30-50MB on average. So you add 95.1MB on top of
that and it will go over the 100MB. Once this limit is reached, we restart
the process, thus resulting in the failure of the download.)
So the reason for this post is. I don't understand how the response buffer
works. Why is it that the data in the response buffer is held in memory. In
my code I always clear the buffer when I'm done with it. How are they
figuring that my site is averaging 30-50MB?
I guess I'm just looking for information, so I can do a work around. Any
pointers would be appreciated.
code
but I could not find anything wrong. So I tested the download by replacing
the 95MB
file with a smaller one (20MB). It worked fine. When I contacted my hosting
company
this is what they told me.
(Data streamed through the Response buffer will be held in memory. We allow
a maximum of 100MB memory usage per site.
The 100MB memory limit is applied to the site's application process. Your
site itself is using about 30-50MB on average. So you add 95.1MB on top of
that and it will go over the 100MB. Once this limit is reached, we restart
the process, thus resulting in the failure of the download.)
So the reason for this post is. I don't understand how the response buffer
works. Why is it that the data in the response buffer is held in memory. In
my code I always clear the buffer when I'm done with it. How are they
figuring that my site is averaging 30-50MB?
I guess I'm just looking for information, so I can do a work around. Any
pointers would be appreciated.