dotnet / dotnet/performance

Is warm up needed ?

Open
#2,199 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
F#
Stars
773
Forks
301
Avg merge
6d 9h
Merged PRs (30d)
15

Description

I have four services developed with **dot net 6**

- I'm using Fix protocol for communication with client(It is a financial protocol built on TCP )
- I'm using grpc unary communication(internal communication)
- I'm using EF , dapper and ado.net
- I'm using redis
- I'm using the default dependency injection in .net
- Most of services are singleton( there are many singleton services and some of them used for just caching some data )

The problem is the first **20 requests latency** is very high compared with the next requests also if the system is **idle for five minutes** ,the request after this idle time **takes a long time**

How can i identify the problem and what is best solution for this problem ?

Shoud i make a warm up service to send fake requests all the time to keep the system warm but this will affect my real request as i expected a lot of requests at the same time?

If the warm up is the solution what is best practise for applying it ?

thanks

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.