* Thus wrote Kim Steinhaug: > Just a quick question, > > Did you alter the upload_max_filesize to 500MB > and the post_max_size to say 510MB and you succesfully > upload 500MB files from one machine to the server? > > I never testes with filesizes that large, but It would be nice to > hear if it accually works without tweaking to much.
It comes down to these settings: php's post_max_size upload_max_filesize and the webserver's max size of data. the link of raditha's, posted earlier in this thread, explains all these setting rather well. > > I would also think that the general 30sec timout would need to > be altered as moving a 500MB file from /var/ to the users homedirectory > and then do some filechecking on it and such would easilly need > some extra seconds. Not to think of the overhead if many people > upload large files at a time. I'm not sure if the actual move is calculated in the script execution time, but it would be wise to take that into consideration when coding. Of course if /var and /usr are on the same mount (evilness), the time to move that file is very fast. The only issue you really have with many people uploading large files is disk space, neither php or apache will not load the whole file into memory, unless you have the php setting always_populate_raw_post_data (always == in certain conditions). There is also the overhead of disk access speed. If a move requires a copy then delete, having many people uploading files will slow the whole system down, in many cases. So if this is the case, it might be best to configure php to use the tmp upload dir to use the same mount point as where you're moving the file to. > > Ok, its a vague post this, just looking for some input here, :D HTH. Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
