Wednesday, 10 May 2017

Why is a static file on Azure served slower when served with Node instad of ASP.NET Core?

(I am unsure whether this is the correct site for this question. If it is, please feel free to remove this disclaimer, otherwise just ping me, I will move and delete it then...)

We are deploying an angular application that has been created using the Angular-CLI toolset to an Azure WebApp. Loading a static file with about 500 KB from a browser takes a good seven seconds in this setup.

When delivering the same file using an ASP.NET Core web application and the app.UseStaticFiles() middleware, the load time drops to less than 200 ms.

Am I missing something about Node.js serving static files here? Can anyone point me at what we did wrong here?



via Spontifixus

No comments:

Post a Comment