Add benchmarks that test the scalability of large requests and large responses

Open
#1,498 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp

Research direction

No files or tests are named. Start by reviewing the related issues #17843 and #21187, then examine the request and response buffering scenarios described here: EnableBuffering, multipart files, JSON.NET formatting, and XmlSerializer formatting. Done means benchmarks measure throughput and memory as concurrency increases for large requests and responses spooled to disk.

Written by the indexing model from the issue text.

Description

ASP.NET uses a buffer to disk then write to request/response in a couple of scenarios:

  • Buffering the request body (via explicit calls to to EnableBuffering)
  • Buffering multipart files
  • Buffering the response body for JSON.NET based formatting and XmlSerializer based formatting

Our defaults today were picked without any measurements, we should measure how throughput and memory as we add more concurrency for these large read and write scenarios where data is spooled to disk.

Related:

cc @Tratcher @pranavkm @rynowak

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.