High CPU overhead monitoring AppSvcAppLogs in App Services
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 404
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 35
Description
A 1st party team reported that they see CPU usage grow by ~3.25 core-hours / hour when they enabled AppSvcAppLogs for a 3.1 .NET Core app logging ~400 ILogger messages/sec. The messages vary from 100-300 characters each. The pricing tier was P2V2 running on Linux. This CPU seems excessive and would be worth investigating. A few questions to answer:
1. Can we reproduce this result with another service that logs similar amounts or is there something unique here?
2. Has .NET Core 6.0 substantially improved perf or is it still an issue?
3. If it is still an issue on .NET Core 6.0, where is the overhead coming from and what are our options to improve it?
We've got a few traces privately but here is the basic idea of what is happening:
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.