Use Blender 2.90.1 in blender-benchmark. #85187

New Issue

Jeroen Bakker · 2021-01-29T10:15:18+01:00

Jeroen Bakker commented

2021-01-29 10:15:18 +01:00

Blender Open Data currently uses Blender 2.90.0 as its latest version. We haven't updated to 2.91 as a new version of the benchmark_script is needed (See #83002 (Add support for Blender 2.91)).
Nevertheless AMD and AWS requested to use the latest Blender 2.90.1 as an important issue has been solved that will allow successful rendering of big scenes using AMD GPUs (See blender/blender@0f72e7c3eb) This is needed for their Q&A process.

I would propose to run the following script on the opendata postgres database. The script will replace the table entries of 2.90 to use 2.90.1.
I haven't been able to test this so I want to go over the process in constructing this script.

I downloaded and installed a development version of the opendata website on my own system.
I copied the checksums part of the WHERE clause from https://opendata.blender.org/benchmarks/metadata/
I copied the checksums in the UPDATE part from https://download.blender.org/release/Blender2.90/blender-2.90.1.sha256
The filenames and file sizes in the UPDATE part are collected from https://download.blender.org/release/Blender2.90/

UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-windows64.zip', size=197632557, checksum='9939127ac90964984f9a4e6982c29dfcd6337d5ae44537b5c8f3aa371414c9d9' WHERE checksum='f51e1c33f6c61bdef86008280173e4c5cf9c52e4f5c490e9a7e4db3a355639bc';
UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-linux64.tar.xz', size=147167824, checksum='054668c46a3e56921f283709f51a35f7860786183001cf2ea9be3249d13ac667' WHERE checksum='d0c9218fa4fc981204d3d187c35b5168b4df4ea71e2e74fb61be1540b935a83c';
UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-macOS.dmg', size=191065008, checksum='a0f2c33714c44c0897e2047a62ac84ad00f27e1daca6f74cdc8ae0f829b19400' WHERE checksum='51a999d21bf50a6e1f8423b9190571403ee1adc1248911207af13ce21599320b';

Before executing I recommend to run the following SQL statement so we could rollback when there is an issue with the statements above.

SELECT * FROM opendata_main_blenderversion WHERE label='2.90';

In order to test if the change is correct we should look at the result of https://opendata.blender.org/benchmarks/metadata/, start blender-benchmark that should download Blender 2.90.1 and start the blender version that is downloaded to verify that the correct version is used.

Blender Open Data currently uses Blender 2.90.0 as its latest version. We haven't updated to 2.91 as a new version of the `benchmark_script` is needed (See #83002 (Add support for Blender 2.91)). Nevertheless AMD and AWS requested to use the latest Blender 2.90.1 as an important issue has been solved that will allow successful rendering of big scenes using AMD GPUs (See blender/blender@0f72e7c3eb) This is needed for their Q&A process. I would propose to run the following script on the opendata postgres database. The script will replace the table entries of 2.90 to use 2.90.1. I haven't been able to test this so I want to go over the process in constructing this script. - I downloaded and installed a development version of the opendata website on my own system. - I copied the checksums part of the WHERE clause from https://opendata.blender.org/benchmarks/metadata/ - I copied the checksums in the UPDATE part from https://download.blender.org/release/Blender2.90/blender-2.90.1.sha256 - The filenames and file sizes in the UPDATE part are collected from https://download.blender.org/release/Blender2.90/ ``` UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-windows64.zip', size=197632557, checksum='9939127ac90964984f9a4e6982c29dfcd6337d5ae44537b5c8f3aa371414c9d9' WHERE checksum='f51e1c33f6c61bdef86008280173e4c5cf9c52e4f5c490e9a7e4db3a355639bc'; UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-linux64.tar.xz', size=147167824, checksum='054668c46a3e56921f283709f51a35f7860786183001cf2ea9be3249d13ac667' WHERE checksum='d0c9218fa4fc981204d3d187c35b5168b4df4ea71e2e74fb61be1540b935a83c'; UPDATE opendata_main_blenderversion SET url='https://opendata.blender.org/cdn/Blender2.90/blender-2.90.1-macOS.dmg', size=191065008, checksum='a0f2c33714c44c0897e2047a62ac84ad00f27e1daca6f74cdc8ae0f829b19400' WHERE checksum='51a999d21bf50a6e1f8423b9190571403ee1adc1248911207af13ce21599320b'; ``` Before executing I recommend to run the following SQL statement so we could rollback when there is an issue with the statements above. ``` SELECT * FROM opendata_main_blenderversion WHERE label='2.90'; ``` In order to test if the change is correct we should look at the result of https://opendata.blender.org/benchmarks/metadata/, start blender-benchmark that should download Blender 2.90.1 and start the blender version that is downloaded to verify that the correct version is used.

Jeroen Bakker self-assigned this 2021-01-29 10:15:18 +01:00

Jeroen Bakker commented

2021-01-29 10:15:18 +01:00

Added subscriber: @Jeroen-Bakker