Npgsql counters seem to be wrongly-managed

Open
#1,551 5 comments 0 reactions 1 assignee View on GitHub

@roji is already working on this.

Since Jun 16, 2020.

Assessment

This issue has not been assessed yet.

Description

Not sure yet if it's in Npgsql itself or in the benchmark infra, but:

Bytes Written:                     6,483,583
Bytes Read:                        165,323,803
Command Rate:                      0
Total Commands:                    1
Current Commands:                  -6,212,390
Failed Commands:                   0
Prepared Commands Ratio:           0
Connection Pools:                  1
Idle Connections:                  51
Busy Connections:                  16
Commands per multiplexing batch:   25
Waits per multiplexing batch:      0
Time per multiplexing batch (us):  67
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.