Yes, I was referring specifically to the knowledge behind the reply from AMD
Even when measuring raw syscall latency I think you'd need to define a workload for that. Part of the overhead is going to be around TLB management & hit ratio, which'll be heavily dependent on workload.
-
-
FWIW, for a memory resident OTLP readonly postgres benchmark with 16 connections, on my i7-6820HQ the performance regression is a bit above 7%.
-
yeah, I don't doubt it can be significant, but a lot of discussion on the topic I've seen has been "regression of X%" without specifying what workload that's with at all so, what defines the overhead of the TLB swap? Number of memory maps? (getting way out of my depth here)
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.