Performance comparison between different server machines

Open
#1,946 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
performance

Research direction

Start with the benchmark results linked in the issue and review how the existing machine categories and measurements are presented. Determine what comparison methodology would account for CPU, networking, and client/server placement; done would mean an agreed approach or documented conclusion, but no implementation files or tests are identified.

Written by the indexing model from the issue text.

Description

In your benchmark results (https://aka.ms/aspnet/benchmarks), there are many machines listed like Intel Linux, AMD Linux, Azure Arm64 Linux, etc. Apart from the cpu, I'm assuming all of these machines have different parts like networking chipsets, drivers, motherboards.

Currently, I believe you are tracking performance within a single machine and not making comparisons between different machines. I'm curious what would be the best way to make cpu performance comparisons between different machines while running ASP.NET if they're using different parts, especially network chipsets? Ie, does server machine A perform better than server machine B on a given ASP.NET benchmark?

Would it be recommended to run the whole benchmark (client and server) on the same machine? That way, the effects of different networking parts could be eliminated, but this also introduces other factors such as resource contention between the client and server.

Thanks

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.