dotnet/aspnetcore

Performance of Rewrite Middleware

Open

#5,981 opened on Aug 4, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
area-middlewarefeature-rewrite-middlewarehelp wanted

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

The whole rewrite middleware needs to be profiled. Specifically, checking for hotspots in the actual application of rules, which matters significantly more than startup time. Memory allocation should be checked too.

Contributor guide

Research direction
Profile the rewrite middleware using dotnet trace or PerfView. Focus on runtime performance of rule application and memory allocations. Identify heavy allocations or slow paths and provide optimization suggestions.
Tech stack
csharp
Domain
backend
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
C#dotnetprofiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30