4 ms·
I think the choices of these workloads are deliberate, considering this is a large core count CPU linked to a FP-monster GPU with a high speed, low latency data
by torginus 2mo ago
I think the choices of these workloads are deliberate, considering this is a large core count CPU linked to a FP-monster GPU with a high speed, low latency datalink.
The former implies per core memory bandwidth is probably not great, meaning SQLite wont perform as well, the latter meaning FP workloads are better done on the GPU, so video encoding wont be a high point. The idea is to run branchy integer workloads that fit into RAM imo, which is what these benchmarks measure.