3 ms·
> c8g.8xlarge (32 core non-NUMA ARM64) Requests are scheduled on half of these. Despite that, a plateau is hit after 8 threads? Is this a 16-core 32-thread typ
by phoronixrly 1y ago
> c8g.8xlarge (32 core non-NUMA ARM64)
Requests are scheduled on half of these. Despite that, a plateau is hit after 8 threads? Is this a 16-core 32-thread type of a setup?
Also, consider redoing this in linear scale.
Edit: Oddly enough, no? 1 thread per core as per https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cpu-options-supported-instances-values.html#cpu-options-compute-optimized https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cpu-opti...
- swiftcoder 1y ago> a plateau is hit after 8 threads? Most of the graphs plateau around 6 threads, for pretty much all the caches under test. I wonder if there is some interesting architectural issue with cache-sharing on this particular platform?
- namibj 1y agoI guess memory controller behavior; especially if it's not set up for parallelism IOPS but for single-threaded throughout (channel interleaving).
- everfrustrated 1y agog = graviton which doesn't support SMT so 1 vcpu is 1 full core
- tidwall 1y agoThanks for the feedback. The plateauing is due to a taskset misconfiguration. I fixed it and reran the benches. They look much better now.