3 ms·
> The upper bound is somewhere around 500 million transactions per second per core. What’s the definition of transaction here? That’s a transaction for every ~
by sokoloff 5y ago
> The upper bound is somewhere around 500 million transactions per second per core.
What’s the definition of transaction here? That’s a transaction for every ~6 (peak ~10) clock cycles.
https://www.agner.org/optimize/instruction_tables.pdf https://www.agner.org/optimize/instruction_tables.pdf
- bob1029 5y agoTransaction in this context being "Place order", "Cancel order", "Update user settings", etc. We need to remember there isn't a 1:1 relationship between instruction/clock rate and the number of actual instructions that are retired per unit time. Pipelining and ILP allow for speedups that range anywhere from 1-100x depending on the specific flavor of application.