---
title: "Comment by Arnold Holm on \"Measuring Latency in .NET Without Fooling Yourself: Stopwatch, Percentiles and Coordinated Omission\" | Hashnode"
description: "The fixed-rate test should also keep timed-out and rejected orders in the report. A histogram of completed fills alone can look faster when the slowest requests"
url: "https://hashnode.com/posts/measuring-latency-in-net-without-fooling-yourself-stopwatch-percentiles-and-coordinated-omission/6abe6f61ad1bec9939b37493/comment/6ac79db9ee187fa2254072ac"
---

[Discussion](https://hashnode.com/posts/measuring-latency-in-net-without-fooling-yourself-stopwatch-percentiles-and-coordinated-omission/6abe6f61ad1bec9939b37493)

Comment [Measuring Latency in .NET Without Fooling Yourself: Stopwatch, Percentiles and Coordinated Omission](https://hashnode.com/posts/measuring-latency-in-net-without-fooling-yourself-stopwatch-percentiles-and-coordinated-omission/6abe6f61ad1bec9939b37493)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 8](https://hashnode.com/posts/measuring-latency-in-net-without-fooling-yourself-stopwatch-percentiles-and-coordinated-omission/6abe6f61ad1bec9939b37493/comment/6ac79db9ee187fa2254072ac)

The fixed-rate test should also keep timed-out and rejected orders in the report. A histogram of completed fills alone can look faster when the slowest requests disappear. Record each intended request and its final status, then show the timeout/rejection counts beside the latency percentiles. That makes the tail visible even when no fill arrives.
