Benchmark fails for scene Victor #73648

New Issue

rob · 2020-02-06T21:24:40+01:00

rob commented

2020-02-06 21:24:40 +01:00

System
Linux 64bit Gentoo
16GB Ram
Over 100GB free disk space (directly available)
Nivida GeForce GTX 1660 Ti
Intel i5-9400f 2.90GHz

Environment
blender-benchmark-cli 2.0.4
blender-benchmark 2.0.4

Issue
Benchmark (GUI or CLI) fails when Victor is included as a scene to render.

All other scenes work fine.

Using 2.81 or 2.81a has the same result (fails for Victor, works for all others)
Using GPU or CPU has the same result (fails for Victor, works for all others)

Have tried "clear_cache" option and manually deleting ~/.cache/blender-benchmark-launcher/

Running

benchmark-launcher-cli benchmark --verbosity 3 --blender-version 2.81a --device-type CUDA --json --submit victor

results in
https://pastebin.com/4VWZ5tuA (415.03 KB)

but I cannot see an obvious issue, other than its fails on "Updating Scene BVH | Building BVH"

My system is

Happy to provide any other information on request. Have previously submitted the error using the benchmark GUI.

**System** Linux 64bit Gentoo 16GB Ram Over 100GB free disk space (directly available) Nivida GeForce GTX 1660 Ti Intel i5-9400f 2.90GHz **Environment** blender-benchmark-cli 2.0.4 blender-benchmark 2.0.4 **Issue** Benchmark (GUI or CLI) fails when Victor is included as a scene to render. All other scenes work fine. Using 2.81 or 2.81a has the same result (fails for Victor, works for all others) Using GPU or CPU has the same result (fails for Victor, works for all others) Have tried "clear_cache" option and manually deleting ~/.cache/blender-benchmark-launcher/ Running ``` benchmark-launcher-cli benchmark --verbosity 3 --blender-version 2.81a --device-type CUDA --json --submit victor ``` results in https://pastebin.com/4VWZ5tuA (415.03 KB) but I cannot see an obvious issue, other than its fails on "Updating Scene BVH | Building BVH" My system is Happy to provide any other information on request. Have previously submitted the error using the benchmark GUI.

rob commented

2020-02-06 21:24:40 +01:00

Added subscriber: @rob_on_earth-1

Ray molenkamp commented

2020-02-06 22:08:30 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2020-02-06 22:08:30 +01:00

peak memory for victor on my box is 16774.97M that 16GB of ram may be just a little short there.

Sem Mulder commented

2020-02-12 09:31:35 +01:00

Added subscriber: @SemMulder

Sem Mulder commented

2020-02-12 09:31:35 +01:00

Changed status from 'Needs Triage' to: 'Resolved'

Sem Mulder closed this issue

2020-02-12 09:31:35 +01:00

Sem Mulder self-assigned this 2020-02-12 09:31:35 +01:00

Sem Mulder commented

2020-02-12 09:31:35 +01:00

I believe @LazyDodo is correct here. We are currently still investigating how to detect this properly (detecting the amount of GPU memory available across all brands is a bit complicated). Closing this for now as this is not an issue with the launcher per se.

rob commented

2020-02-14 00:00:25 +01:00

I tried the Victor scene with an unrelated Windows laptop with 16GB ram and it had the same result.

Setting the number of Samples to 1 and the render size to 10% manually allowed it to complete, so I agree, it is running out of memory in the benchmark.

FYI the Victor scene opens with a text window suggesting 12GB

I tried the Victor scene with an unrelated Windows laptop with 16GB ram and it had the same result. Setting the number of Samples to 1 and the render size to 10% manually allowed it to complete, so I agree, it is running out of memory in the benchmark. FYI the Victor scene opens with a text window suggesting 12GB

This repo is archived. You cannot comment on issues.