Blender Benchmark Thread

Steinwerks · August 20, 2018, 1:04am

Well, running Full Benchmark. Pretty sure it was just running Quick CPU last time. CPU is still at stock.

Edit: taking full CPU load but no GPU.

tkoham · August 20, 2018, 1:18am

you have to do a gpu run for it to use the GPU. That’s how cycles works.

did you try passing the (corrected from typo) env variable?

Steinwerks · August 20, 2018, 1:29am

I tried?

Honestly I’m about to give up, I have other things to do this evening.

tkoham · August 20, 2018, 1:30am

you just do exactly what you did before but without the typo. the gpu test should run.

Steinwerks · August 20, 2018, 1:31am

It doesn’t.

It spikes and then drops off to nothing again.

tkoham · August 20, 2018, 1:34am

does the gpu show up as an option for the render test?

Steinwerks · August 20, 2018, 1:38am

Yes and I chose it. I give up for now, need to eat dinner and spend time with the wife. I’ll do my best to try more tomorrow evening.

tkoham · August 20, 2018, 1:39am

then my guess would be that

it’s a driver issue
they locked down env variables for the benchmark to retain consistency

ajc9988 · September 8, 2018, 4:25pm

So, here is my result. Aside from just posting the main overall time, especially because it doesn’t show whether you ran the complete or quick test, please copy and paste the results from the website after logging in. It gives data like the time to complete on each task. Here is my Complete score for CPU in my current linux build using Kernel 4.19rc-2 generic (I didn’t prep my kernel so that when I installed the Nvidia proprietary driver, it broke; I’m a linux noob, but found a page on what exactly happened and how to avoid the problem next time).