A few points: * The reason for the 100meg limit has to do with php and apache and how it stores the uploaded POST in memory so setting the limit higher would risk increasing chances of apaches hitting swap if multiple uploads happened on a given box.
* Modern html5 browsers are starting to be able to natively split files up into chunks and do separate 1 meg xhr posts. Firefogg extension does something similar with extension javascript. * The server side chunk uploading api support was split out into an extension by Mark Hershberger ( cc'ed ) * We should really get the chunk uploading "reviewed" and deployed. Tim expressed some concerns with the chunk uploading protocol which we addressed client side, but I don't he had time to follow up with proposed changes that we made for server api. At any rate I think the present protocol is better than normal http POST for large files. We get lots of manageable 1 meg chunks and a reset connection does not result in re-sending the whole file, and it works with vanilla php and apache ( other resumable http upload protocols are more complicated and require php or apache mods ) * Backed storage system will not be able to handle a large influx of large files for an extended period of time. All of commons is only 10 TB or so and is on a "single" storage system. So acompaning an increase of upload size should be an effort / plan to re-architect the backed storage system. --michael On 07/20/2010 09:32 AM, Daniel Kinzler wrote: > Lars Aronsson schrieb: > >> What are the plans for increasing this limit? Would it be >> possible to allow 500 MB or 1 GB for these file formats, >> and maintain the lower limit for other formats? >> > As far as I know, we are hitting the limits of http here. Increasing the > upload > limit as such isn't a solution, and a per-file-type setting doesn't help, > since > the limit strikes before php is even started. It's on the server level. > > The solution are "chunked uploads". Which people have been working on for a > while, but I have no idea what the current status is. > > -- daniel > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
