1

I am working on .net core API where i had to finalize an approach for copying files. File Size may vary from 1 MB to 25 MB. Currently we are getting 20 to 25 k hits per second. Is there any solution Or approach where multiple request can be handled with low memory usage.

Is there something like transmitFile in .net Core?

Supreet
  • 2,451
  • 8
  • 25
  • 42
  • 1
    Doesn't address your question directly, but you should take a look at this question too: https://stackoverflow.com/questions/57591344/why-asp-net-core-2-2-do-not-release-memory – user743414 Jan 07 '20 at 12:14
  • 1
    In general, you should return a stream, unless you have already read from the stream. If you're doing some sort of operation that requires the file being loaded into memory (such as resizing an image, for example), then it's already too late. If you're just returning a file directly, then return a `FileStreamResult`, and it will be as efficient as it ever can be. – Chris Pratt Jan 07 '20 at 14:11

1 Answers1

1

First thing that comes to mind, when you are dealing with I/O bound operation such as DB or file system, would be to make sure you deal with everything in an asynchronous way. You don't want your process to stop because you are waiting for your hard drive to finish. Dot Net Core is massively using it and the syntax is fairly simple, the concept behind it, though, is not often well understood. You could have a look at article such as https://ayende.com/blog/173473/fun-async-tricks-for-getting-better-performance if it is not completely clear to you.

Then, on top of it, if you want to avoid allocating to much memory on the server, you should be careful reading the file bit by bit instead of loading the full 25Mb as soon as you enter your code.

Async + small buffer should make it as performant and low-foot-print as possible.

Daboul
  • 2,635
  • 1
  • 16
  • 29