Kestrel perf counters are only partially shown depending on other perf counter providers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- performance
Research direction
Reproduce the output with only the Microsoft-AspNetCore-Server-Kestrel provider, then add the other providers and compare the displayed sections. Trace the perf-counter output formatting around provider aggregation; done when the complete Kestrel statistics remain visible alongside other providers.
Written by the indexing model from the issue text.
Description
When running with only the Microsoft-AspNetCore-Server-Kestrel perf counter provider, I'm getting nice full stats:
## Kestrel:
Connections/s (max): 514
Connections: 1,027
TLS Handshakes/sec (max): 0
TLS Handshakes: 0
TLS Handshakes (max): 0
Failed TLS Handshakes (max): 0
Concurrent Connections (max): 512
Connection Queue Length (max): 0
Request Queue Length (max): 0
Upgraded Requests (max): 0
But weirdly, when adding other providers, it seems that output is truncated somehow:
## System.Runtime:
CPU Usage (%): 95
Working Set (MB): 472
GC Heap Size (MB): 309
Gen 0 GC (#/s): 2
Gen 1 GC (#/s): 1
Gen 2 GC (#/s): 0
Time in GC (%): 1
Gen 0 Size (B): 10,819,264
Gen 1 Size (B): 3,060,552
Gen 2 Size (B): 21,146,776
LOH Size (B): 191,672
Allocation Rate (B/sec): 711,745,520
# of Assemblies Loaded: 86
Exceptions (#/s): 66
ThreadPool Threads Count: 28
Lock Contention (#/s): 918
ThreadPool Queue Length: 0
ThreadPool Items (#/s): 230,266
## Kestrel:
Connections/s (max): 514
TLS Handshakes/sec (max): 0
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 244
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aspnet/Benchmarks
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
aspnet/Benchmarks#2226 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aspnet/Benchmarks#2015 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/Benchmarks#2204 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aspnet/Benchmarks#2161 ·
-
Test io_uring impactOpen
Difficulty 4/5 3-5 days Newbie friendliness 20/100
aspnet/Benchmarks#2153 · 21 reactions ·
All issues in aspnet/Benchmarks
Similar issues
-
area-NavigationView bug needs-triage team-Controls
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/microsoft-ui-xaml#12671 · 3 comments ·
Maintainers usually reply within 2 days
-
Retarget the extension to Fallout 10.5Possibly taken @ChrisonSimtian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Improve time codes: status hint doesn't mention the new Shift+F7 / Shift+F8 "to check" navigationOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SubtitleEdit/subtitleedit#16943 ·
Maintainers usually reply within 1 day