Kestrel perf counters are only partially shown depending on other perf counter providers

Open
#1,550 3 comments 0 reactions 0 assignees View on GitHub

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aspnet/Benchmarks

All issues in aspnet/Benchmarks

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.