miniprofiler
for backend engineers
Why this scored 11
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 116
BenchmarkDotNet vs. MiniProfiler for identifying performance bottlenecks in an ASP.NET Core service
Benchmarks compare BenchmarkDotNet and MiniProfiler for ASP.NET Core performance profiling. · for backend engineers
stackoverflowSteadydevtools43d ago - 214
What is the difference between MiniProfiler's request duration and action duration?
Explains the distinction between request and action timings in MiniProfiler for ASP.NET MVC. · for .NET developers
stackoverflowSteadydevtools48d ago