Optimizing Large File Uploads

ASP.NET is built in such way that all client requests are kept in memory as one data thread. In many cases this allows drastically improved system performance and reduced time it takes to process each request. But, when you upload large files the system performance goes down proportionally to file size because more memory and processor power is used to process such requests. This can lead to a number of stability problems and even a server crash.

Mediachase FileUploader.NET provides multi level file upload optimization capabilities.

The Following list provides an overview of the optimization process:

• Only post requests that contain files are optimized.
• File(s) uploaded without page submitting.
• Data is handled before ASP.NET processing starts.
• Files in post-request state are saved in temporary file storage and replaced with active markers with fixed size (a few bytes).  This allows for making the post request fixed in size.
• Temporary files that are used during upload are deleted after requests are completed.

Example Performance Monitor Snapshots:

Page File Usage History with Mediachase FileUploader.NET: