|
|
|
|
|
by murkt
62 days ago
|
|
> writing “90 kBq” is a lot more convenient than “ninety thousand requests per second” and “90,000 requests/s” I once made a joke during the talk that MongoDB is better than Postgres in two ways, and one of those ways is that it’s faster to say “Mongo” than “Post-gres-Qu-eL”. Same vibe here. 90krps is not that longer than 90kBq. With requests per minute, rpm: engine in my car revs up to 9000 requests per minute! It’s sometimes funny to see some marketing posts like “we built our infrastructure to handle UNREAL load during the event, 100 million of requests during the day.” Which is just a bit more than 1100 rps. |
|
The only problem with that unit is that it may require explaination. Hertz is a little bit more commonly understood, while someone seeing 2.5 Bq will very likely wonder what that means.
In the end both Hz and Bq resolve to s⁻¹ or 1/s So maybe request/s is just okay as a unit? In the end it depends also on the surrounding UI.