SI Units for Request Rate (2024)

Lobsters Hottest News

Summary

An article discussing the proper use of SI units for measuring request rate in distributed systems, proposing the use of hertz (Hz) for periodic/regular traffic and becquerel (Bq) for stochastic/organic traffic patterns to standardize how request rates are communicated.

<p><a href="https://lobste.rs/s/x5hnnp/si_units_for_request_rate_2024">Comments</a></p>
Original Article
View Cached Full Text

Cached at: 04/20/26, 02:55 PM

# SI Units for Request Rate Source: [https://entropicthoughts.com/si-units-for-request-rate](https://entropicthoughts.com/si-units-for-request-rate) *Request rate*is the number of requests that arrive, or are serviced, or leave, during some period\. It’s surprisingly common for people to speak of a request rate without specifying what the length of the period is\. I have even seen dashboards that don’t have a fixed period for the metrics query – the request rate becomes measured per whatever aggregation interval the dashboard deems appropriate for the window size at the time\. If you zoom out, you get a higher request rate\. If you move the window to a high\-resolution screen, you get a lower request rate\. We should specify the period length in the query to the metrics database, so everyone sees the same request rate regardless of how many pixels their dashboard occupies at the time\. The good period length to use is the second\. Request rates should be measured as the number of requests per second\.11I have met some people who measure requests per minute\. Don’t be those people\.This sounds like it would have ansiunit, i\.e\. we should be able to say something like “our request rate is 57 watts\.” Except obviously not watts\. --- Turns out there are twosiunits that both could fit: - The hertz, or Hz, is thesiunit of frequency\. It is defined as one event per second\. - The becquerel, or Bq, is thesiunit of \(radio\)activity\. It is also defined as one event per second\. Why are there two units for the same thing? A physicist that hears that an event occurs at 4 Hz will assume that there is one event exactly every 250 milliseconds\. The hertz unit is strongly associated with periodic behaviour\. Radioactive decay is not that well behaved, and will happen only on average with the given frequency\. A sample that decays at 4 Bq may decay zero times one second, and then 9 times the next\.22Assuming a Poisson distribution, these will be rare events, but if you look at the sample for an hour, you have a better than 50 % chance of observing that exact sequence of decays\. It makes sense then that we would say the request rate is 500 Hz when we talk about highly regular load testing, where one request is issued consistently every 2 ms\. But if it’s about organic traffic that happens to arrive at an average of 500 times per second, then maybe saying 500 Bq is more appropriate\. This is also convenient when we are nearing request rates static web servers or caches handle\. Saying “ninety kilobecquerel” and writing “90 kBq” is a lot more convenient than “ninety thousand requests per second” and “90,000 requests/s”\.33A reader suggested inventing the unit “rips” instead, which I like both the idea and sound of, but I’m a sucker for bending standards to my will\. --- *Except*\! It seems that – in contrast to the hertz which is a general unit – the becquerel is meant to be specifically about radioactive decay\. There’s nosiunit for arbitrary events that happen on average with a certain frequency\. I will keep using the becquerel for request rates, and I hope that 50 years from now, we will have forgotten the silly mistake of thinking it was only about nuclear decay\.

Similar Articles

UniSVQ: 2-bit Unified Scalar-Vector Quantization

arXiv cs.CL

UniSVQ proposes a unified 2-bit quantization framework that bridges scalar and vector quantization by parameterizing codewords as an affine transform of integer lattices, achieving state-of-the-art performance among scalar methods and matching vector methods with higher throughput.

Qwen3.6-27B Quantization Benchmark

Reddit r/LocalLLaMA

This article benchmarks various Qwen3.6-27B quantizations (Q8 to Q2) using KLD and Same Top P metrics, comparing providers like Unsloth and mradermacher, and offers recommendations for quality-size trade-offs.

Elucidating the SNR-t Bias of Diffusion Probabilistic Models

Hugging Face Daily Papers

This paper identifies a Signal-to-Noise Ratio timestep (SNR-t) bias in diffusion probabilistic models during inference, where SNR-timestep alignment from training is disrupted at inference time. The authors propose a differential correction method that decomposes samples into frequency components and corrects each separately, improving generation quality across models like IDDPM, ADM, DDIM, EDM, and FLUX with minimal computational overhead.

We should get rid of average CPU utilization

Hacker News Top

The article explains why average CPU utilization is a misleading metric for latency-sensitive workloads, using queueing theory and a real-world production incident. It argues for more nuanced monitoring approaches.