Quote:
Originally Posted by AndrewD
I never dreamed that this would end up being a heavyweight....
First thing to work out is whether it is the load on the database that is killing your server, or the physical effort of transferring the files which are being downloaded. I would be inclined to suspect the second - recall that the files themselves are not stored in the database.
Second, how are the urls being specified for the downloads? If they are being entered as full urls (even if this is the same server), this is a sure fire recipe for hammering the server. Far better to have the files specified using a local filename (or uploaded, which amounts to the same thing)..
|
Hey, if you would stop providing such wonderful customer support.. we would stop using the program

Okay really, please don't!! We're about to create a gold shrine in your honor.
We'll go ahead and start with storing the files on the server that is solely dedicated to downloads... and see how that works. I do know that we get SQL errors when this happens, so that's why I'm assuming it's to much work on the database instead of the server itself.
The problem that I have had w/ the full urls/local filename is that we've never been able to get it working on our server. Anything over 5MB fails, so we have to do the full URL. We upped our PHP Maximum Upload Size to 50.00 MB.. still didn't help.. but I'm guessing I didn't do something right somewhere. I'll do some more reading about this because I think I did see you had posted something about this situation in this thread.