.net core 7 web api very slow first call more that 32s

Pedro Manuel Moço Ramalho 16

Hi,

I have a problem in EF7 with core 7 web api. The first call take more that 30s and the second call take 60ms what is good. Any solution for that?

Thanks

Zhi Lv - MSFT 32,011 Reputation points Microsoft Vendor

2023-01-24T05:18:03.55+00:00

Hi @Pedro Manuel Moço Ramalho

Whether this issue happens on local/development environment or production environment? Try to use F12 developer tools, enable logging or use some Performance Diagnostic Tools to check which part will spends too time to load?

Generally, the first request might still be slower due to several reason (such as Authentication, some of which may be client-side like DNS requests, or network-related lost packets, poor internet connection, IIS configuration for the application pool etc). Then after the application start and first request, it might use cache to store some resource, then, it will reduce the request time from the second call.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

3 answers

Pedro Manuel Moço Ramalho 16 Reputation points

2023-01-27T12:14:21.9433333+00:00

Hi,

I try but nothing at this time is soluction for problem, I have de same call in Framwork 4.7 and work well in the same server.

Any sugestion?

Thanks
Please sign in to rate this answer.

1 person found this answer helpful.
Zhi Lv - MSFT 32,011 Reputation points Microsoft Vendor

2023-01-31T02:47:45.7966667+00:00

Without any of code, log information or performance diagnostic result, it is hard to find out where exact the time is spent. So, in order for us to investigate this issue, can you provide a minimal project (ideally a GitHub repo) that illustrates the problem.
Sign in to comment
Srivastava, Prashant 1 Reputation point

2023-01-31T09:31:49.22+00:00

@Pedro Manuel Moço Ramalho you might wanna check first the sequence of middleware you are calling to see what all kinds of middleware you have in call hierarchy and before it actually make a call to your end point what you are doing (starting from Startup.cs ) which is when you launch the API or say make the very first call to API.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Aravind Kumar Eriventy 0 Reputation points

2023-04-05T09:16:45.8933333+00:00

I think the issue is with DotNet Core, I had the same issue in one of my projects, The first call from dotnet core is taking more time to respond to, but this is not the case from Framework 4.7, both projects are having the same code, the same middleware and the same layers. To solve the issue I used app.UseResponseCompression, and added Microsoft.AspNetCore.ResponseCompression NuGet package into my project and configured it in the Startup class. The above solution works fine only for a day,
I don't know why taking more time to respond using the Dotnet Core.
Please sign in to rate this answer.
Pedro Manuel Moço Ramalho 16 Reputation points

2023-04-05T10:45:03.1966667+00:00

I have made a lot of simulation, but nothing get more performance to the project. I don't know what doing more.

Stefano Fabiano 0 Reputation points

2023-04-28T12:59:16.9533333+00:00

Do you have a big (many datasets) or may be complex (many complex relations) Context Model?
This can be the cause of the problem. As described in the linked video below, at the first access to the dbcontext it needs to be built and it can takes time if it's big or complex, from there it's cashed and it becomes faster.
You can try to precompile the model at design time to speed up the first access, but in this case some functionalities are not supported, like for example global query filters or lazy loading.

https://www.youtube.com/watch?v=FYz0rAxQkC8&list=PLdo4fOcmZ0oX0ObHwBrJ0vJpZ7PiYMqeA&index=1
Sign in to comment