Again, I think your logic here is flawed. It’s still valuable to know how a single core behaves for a rendering work load.
I’ve worked professionally in feature film production. We test single threaded performance all the time.
It tells us the performance characteristics of the nodes on our farm, and lets us more accurately get a picture of how jobs will scale and/or be packed.
It’s not uncommon to have a single thread rendering, for example to update part of an image while an artist works on other parts.
It’s not just a test of how wide the chip is. It also tests things like how it actually handles the various instruction sets from a real world codebase. Not all processors that are equally “wide” (not the right term but whatever) handle AVX the same, and you need to know how a single core behaves for that. It’s also useful to see how the cores actually behave on their own so you can eliminate the overhead of thread synchronization and system scheduling affecting you.
I’ve worked professionally in feature film production. We test single threaded performance all the time.
It tells us the performance characteristics of the nodes on our farm, and lets us more accurately get a picture of how jobs will scale and/or be packed.
It’s not uncommon to have a single thread rendering, for example to update part of an image while an artist works on other parts.
It’s not just a test of how wide the chip is. It also tests things like how it actually handles the various instruction sets from a real world codebase. Not all processors that are equally “wide” (not the right term but whatever) handle AVX the same, and you need to know how a single core behaves for that. It’s also useful to see how the cores actually behave on their own so you can eliminate the overhead of thread synchronization and system scheduling affecting you.