QRNG throughput explained, why 1 Gbit/s matters and when it does not
Entropy throughput matters only in relation to how fast a system consumes it. The sizing calculation is reseed interval multiplied by concurrent DRBG instances, plus any bulk consumption; for most workloads that lands far below a gigabit per second, and for a few it lands above it.
Why the headline number is usually the wrong question
Entropy rate is the specification vendors compete on because it is a single number that can be made larger. It is rarely the binding constraint. A system generating a few thousand keys a second needs a tiny fraction of what a modern source produces.
The number becomes relevant in specific situations: reseeding many DRBG instances frequently, provisioning devices in manufacturing where every unit needs its own secret, or a security policy requiring fresh entropy per operation rather than periodic reseeding.
The calculation
Work out what you consume rather than what the source produces. Multiply the number of DRBG instances by the seed size, divide by the reseed interval, and add anything that consumes entropy directly rather than through a DRBG. That is your floor.
Then add headroom for the case that actually breaks systems: the burst. Steady-state consumption is easy to satisfy and a reconnection storm after an outage is not, because every session re-establishes at once. Sizing to the average is how a system that was comfortable for a year fails on the worst day.
Where rate turns into architecture
Once consumption is high enough that a single source cannot serve every consumer, you face a distribution question — and the answer that matters is where the source sits relative to what needs it. Entropy that has to travel between security boundaries stops being local, and the argument for a physical source is substantially an argument about locality. This site does not treat entropy as something to deliver over a network.
The alternative is to put a source in each place that needs one, which is viable exactly because the source became a semiconductor part rather than an instrument. Form factor is where that choice is made.
Keep reading
- Deployment and integration
QRNG for HSMs and PKI
An HSM generates keys that protect everything else, so the entropy source inside it is the root of the whole hierarchy. What matters for an HSM or a certificate authority is not only that the source is physical, but that its entropy claim is evidenced within the module boundary and can be demonstrated during evaluation and audit.
- Deployment and integration
QRNG form factors, from PCIe card to silicon IP
Quside supplies entropy sources as PCIe cards, FMC modules, embedded modules and licensable silicon IP. The choice is governed by where entropy needs to be generated relative to what consumes it, and by how many units you are building.
- Deployment and integration
Integrating a QRNG: C, Python, Rust and the Linux entropy path
On Linux a hardware entropy source is normally exposed through the kernel random subsystem, so applications keep calling getrandom() and inherit the better seed without changing. Direct access through a device interface or a library is available where an application needs entropy that has not passed through the kernel pool.