1

I have the single big file (1.2GB+) hosted on the server to download currently served using HTTP/1.1.

We are exploring if we can move to HTTP/2 for better performance and security.

All the places on the internet I see people talking about improvement in speed if there are many small files I need to download. What about a single big file?

  • 2
    Why don't you test it? I doubt setting up a webserver for a single static file takes that much time. – nvoigt May 4 at 7:43
  • True. I set up ASP.Net Core server and find out HTTP2 has 25% better performance. Though I read all around that it is designed for multiple small resources. I cannot up the changes on production unless sure about the results. Both theoretical and practical. – Pranit Kothari May 4 at 15:00
  • Maybe a good candidate for a CDN? – svidgen May 4 at 16:36
1

You are correct. H2 is designed to multiplex many simultaneous requests, and overcome the limitations of TCP in that regard.

Even if you broke up your file into smaller parts, H2 doesnt help you if the contents of all of the file fragments are needed to be useful.

Even gzip etc makes it tough with a file that big. I think you honestly need to look at using FTP, or some sort of background file transfer technique.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.