This is a project about Blender's benchmark bundle and website. Both of this projects are highly under development, more information will be available once things are stabilized and ready for public tests.
Details
Mon, May 2
As far I can see in the data, this is not a specific Quadro k2200 issue, because there were several successful submissions with this card before.
Wed, Apr 20
Classroom may be older but is still a 2.8.x Blender demo file.
The source code is here, I don't know if there is documentation outside of that.
https://developer.blender.org/source/blender-open-data/
Also, where can I find documentation on how the Open Data Benchmark performs its Benchmark ? What are the settings for the files you are computing ? Why and how those settings were chosen ? How can I correlate the Open Data Benchmark results with what I can expect to see in Blender ?
@Brecht Van Lommel (brecht) What is the CPU score of Junkshop on your 16G machine ?
Ok, perhaps the junkshop scene is running out of memory and causing issues on both CPU and GPU. Swapping and running very slowly on the CPU, and just failing on the GPU.
@Brecht Van Lommel (brecht) I'm looking at the number of samples per second at the very end of the log.
@Matthieu (MHEonM1) regarding CPU rendering time, which numbers are you looking at exactly?
Thanks, there is indeed an error that doesn't seem to stop the render:
BLENDER: CommandBuffer Failed: cycles_metal_integrator_reset
@Michael Jones (michael_jones) I guess there are two issues to fix here. One is to stop the render on this error, and the other would be to figure out why the error happens in the first place. Would you have time to look into this?
Here we go.
Likely there is an error while rendering, which causes the render to stop quickly, but this goes undetected and the render time is considered correct.
I am still having nonsensical numbers (13inch MBP M1 8 GPU cores, 8Go RAM), both on CPU and GPU
Since April 10th I see no new unrealistic scores. I don't know if that is a coincidence.
This turned out to be a driver issue that has been fixed in 512.15+.
Apr 6 2022
Mar 28 2022
That is usefull info for the Metal/Blender developers I think if they are going to look into this bug.
Concerning the CPU score of Junkshop:
No problem :)
Sorry for the late response. Here are some screenshots of what I get in OpenData :
Mar 25 2022
I cannot see the low overal scores for Apple M1 CPU scores for junkshop (see screenshot), but I notice quite a large difference between the lowest and highest scores. Is your score specific for your benchmark?
Just to add a precision
The unrealistic values are still being submitted. Because the very high values the overall scores of Apple benchmarks are not really usable:
Mar 22 2022
Hi Sergy,
Mar 21 2022
Need to know system information (windows version, GPU, usual things like that).
Thanks for the report. Sergey, is there anything that we can do to investigate this issue further?
Something similar has been reported by @Pablo Vazquez (pablovazquez) as well.
Mar 19 2022
Mar 18 2022
Good to know the problem is gone!
Thank you for the report.
If the problem reappears, feel free to submit a new report.
Mar 17 2022
I can confirm that I can submit results.
Mar 16 2022
Mar 15 2022
Let's leave the Cycles project out of this. I also suspect the error is no longer relevant given all the changes that went through with Cycles and Open Data.
Feb 21 2022
To clarify, the only remaining issue is the one in your last comment? If it is the case, can you edit report to contain the exact problem as there is currently three problems mentioned?
And are you still able to reproduce it?
Feb 9 2022
Jan 24 2022
Jan 5 2022
Nvidia RTX A5000 here. Windows 10. Won't produce a window when launched. Changed compatibility mode to Windows 8 to get it running.
Dec 20 2021
I just benchmarked with an AMD Radeon RX 6900 XT using Benchmark Launcher 2.0.4 which offers Blender 2.93.1 by now, and the Victor benchmark works now.
Nov 8 2021
Oct 26 2021
Oct 25 2021
Jul 25 2021
Feb 27 2021
Feb 19 2021
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.