Optimizing large file upload

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 improve system performance and reduce time it takes to process each request. But when you upload large files system performace goes down proportionally to file size, because a lot of memory and processor power is used to process such request. This can lead to server crash.

Mediachase FileUploader provides multi level file upload optimization.

Following list provides overview of optimization process:

• Only post requests which can contain files are optimized
• Data is handled before ASP.NET processing starts
• Files in post-request are saved in temporary location and replaced with active markers with fixed size (few bytes), which allows to make post request fixed size
• ASP.NET control element Mediachase.FileUploader.Web.UI.McHtmlFileInput allow to work with active markers
• Temporary files used are deleted after requests are completed
• Optimization Level is specified in configuration file
• Configuration file defined maximum file sizes with ability to redirect to another page

Example:

Page File Usage History without Mediachase FileUploader:


Page File Usage History with Mediachase FileUploader: