Regression: Massive drops in Animation playback (fps) in the viewport #88219

New Issue

Hans Nolte · 2021-05-12T10:31:14+02:00

Hans Nolte commented

2021-05-12 10:31:14 +02:00

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-fedora-36-Rawhide 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44

version	VSYNC	fps solid	fps material	fps rendered
2.92	off	230	80	61
2.93.9 (regression caused by `7f7e683099`)	off	230	76	55
2.93.9 (regression caused by `64d96f68d6`)	off	230	69	46
2.93.9 (regression caused by `267a9e14f5`)	off	230	57	41
3.0.1 (regression caused by `03013d19d1`)	off	200	57	41
3.1.2 (regression caused by `d09b1d2759`)	off	110	57	41
3.2beta (regression caused by `80859a6cb2`)	off	107	54	37

**System Information**
Win 10
GTX 1070 - Studio Driver 462.59

version	VSYNC	fps solid	fps material	fps rendered
2.92	off	223	143	85
3.0 and Cycles-X	off	79	66	50

Short description of error
Massive drops in Animation playback

Exact steps for others to reproduce the error
I have this test scene here from the forum (unfortunately I forgot the direct link).
fps-performance.blend

``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-fedora-36-Rawhide 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 ``` | version | VSYNC | fps solid | fps material | fps rendered | | -- | -- | -- | -- | -- | | 2.92 | off | 230 | 80 | 61 | | 2.93.9 (regression caused by 7f7e683099) | off | 230 | 76 | 55 | | 2.93.9 (regression caused by 64d96f68d6) | off | 230 | 69 | 46 | | 2.93.9 (regression caused by 267a9e14f5) | off | 230 | 57 | 41 | | 3.0.1 (regression caused by 03013d19d1)| off | 200 | 57 | 41 | | 3.1.2 (regression caused by d09b1d2759) | off | 110 | 57 | 41 | | 3.2beta (regression caused by 80859a6cb2) | off | 107 | 54 | 37 | ``` **System Information** Win 10 GTX 1070 - Studio Driver 462.59 ``` | version | VSYNC | fps solid | fps material | fps rendered | | -- | -- | -- | -- | -- | | 2.92 | off | 223 | 143 | 85 | | 3.0 and Cycles-X | off | 79 | 66 | 50 | **Short description of error** Massive drops in Animation playback **Exact steps for others to reproduce the error** I have this test scene here from the forum (unfortunately I forgot the direct link). [fps-performance.blend](https://archive.blender.org/developer/F10087476/fps-performance.blend)

Hans Nolte commented

2021-05-12 10:31:14 +02:00

Added subscriber: @ditos

Philipp Oeser commented

2021-05-12 12:42:15 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-05-12 12:42:15 +02:00

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

Philipp Oeser commented

2021-05-12 12:42:15 +02:00

Can confirm, will bisect.

Philipp Oeser commented

2021-05-12 13:09:14 +02:00

Changed status from 'Confirmed' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2021-05-12 13:09:14 +02:00

Added subscriber: @fclem

Philipp Oeser commented

2021-05-12 13:09:14 +02:00

Apparently caused by 267a9e14f5 (at least for Material and Rendered viewport shading - cannot speak for Solid)

This might all be expected behavior, will let @fclem decide.

Apparently caused by 267a9e14f5 (at least for `Material` and `Rendered` viewport shading - cannot speak for `Solid`) This might all be expected behavior, will let @fclem decide.

Clément Foucault commented

2021-05-12 17:25:19 +02:00

267a9e14f5 may have introduce a bit more overhead but not that much (would expect max 5% change). This seems to affect all modes.

I tried to reproduce but 2.92 & 2.93 & 3.0 release gives me almost exactly the same results (no regression) on a GTX 960M and an AMD Radeon Pro WX7100 on linux. Will try on windows.

Edit: I cannot reproduce the slowdown on windows either (GTX 960).

267a9e14f5 may have introduce a bit more overhead but not that much (would expect max 5% change). This seems to affect all modes. I tried to reproduce but 2.92 & 2.93 & 3.0 release gives me almost exactly the same results (no regression) on a GTX 960M and an AMD Radeon Pro WX7100 on linux. Will try on windows. Edit: I cannot reproduce the slowdown on windows either (GTX 960).

Jesse Yurkovich commented

2021-05-13 06:20:03 +02:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2021-05-13 06:20:03 +02:00

Sadly I can repro here:
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27
High-DPI display (4k so there's lots of pixels to shade)

2.92
Solid: 61fps
Material Preview: 43fps
Rendered: 34fps

3.0 06e62adfb8
Solid: 59fps
Material Preview: 26fps
Rendered: 21fps

Sadly I can repro here: Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27 High-DPI display (4k so there's lots of pixels to shade) 2.92 Solid: 61fps Material Preview: 43fps Rendered: 34fps 3.0 06e62adfb8f2 Solid: 59fps Material Preview: 26fps Rendered: 21fps

Hans Nolte commented

2021-05-13 08:35:58 +02:00

Hi Clément and Jesse,

to prevent the frequency of your monitor from limiting the playback speed,
switch the vertical sync to off.

Hi Clément and Jesse, to prevent the frequency of your monitor from limiting the playback speed, switch the vertical sync to off. ![vertical-sync.jpg](https://archive.blender.org/developer/F10091034/vertical-sync.jpg)

Jesse Yurkovich commented

2021-05-13 09:10:08 +02:00

Thanks for the hint, I edited my comment. I disabled vsync and then used a script to count how long it took to animate across the 250 frames and calculated fps from that. The numbers above should be pretty accurate now. (yeah, even at 4k the default cube scene maxes out at ~70fps for me on both versions so the 60fps numbers there seem right for solid view)

Hans Nolte commented

2021-05-13 09:29:18 +02:00

I have FHD on my GTX 1070 and in Solid 223 fps.
So about four times the fps at a quarter of the resolution, is about right.

I have FHD on my GTX 1070 and in Solid 223 fps. So about four times the fps at a quarter of the resolution, is about right.

Lukas Tönne commented

2021-11-02 10:33:41 +01:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2021-11-02 10:33:41 +01:00

I'm seeing the same issue, on two different machines (both win10, different NVidia cards). Viewport shows 18-25 fps in solid mode, drops to ~12 fps in shaded or rendered.
I have narrowed it down to a combination of armature and subdiv modifiers. Order of modifiers doesn't seem to matter, presumably if the the armature comes first it forces the subdiv to update every frame, or conversely if subdiv comes first it creates more work for the armature deform. The number of bones seems to affect it quite a bit.

Here's a simplified test file:test3.blend

system-info.txt

system-info2.txt

I'm seeing the same issue, on two different machines (both win10, different NVidia cards). Viewport shows 18-25 fps in solid mode, drops to ~12 fps in shaded or rendered. I have narrowed it down to a combination of armature and subdiv modifiers. Order of modifiers doesn't seem to matter, presumably if the the armature comes first it forces the subdiv to update every frame, or conversely if subdiv comes first it creates more work for the armature deform. The number of bones seems to affect it quite a bit. Here's a simplified test file:[test3.blend](https://archive.blender.org/developer/F11676302/test3.blend) [system-info.txt](https://archive.blender.org/developer/F11676190/system-info.txt) [system-info2.txt](https://archive.blender.org/developer/F11676191/system-info2.txt)

Raimund Klink commented

2022-02-23 19:31:39 +01:00

Added subscriber: @Raimund58

Pratik Borhade commented

2022-02-23 19:53:35 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-02-23 19:53:35 +01:00

Can only reproduce on debug build. All release builds works fine here (2.92, 2.93.7, 3.2)
@lichtwerk , can you recheck?

Can only reproduce on debug build. All release builds works fine here (2.92, 2.93.7, 3.2) @lichtwerk , can you recheck?

Jon Henry M. Faltis 9077149 commented

2022-02-23 19:56:15 +01:00

Added subscriber: @geocentric_wage

Philipp Oeser commented

2022-05-13 11:18:29 +02:00

In #88219#1312929, @PratikPB2123 wrote:
Can only reproduce on debug build. All release builds works fine here (2.92, 2.93.7, 3.2)
@lichtwerk , can you recheck?

Getting this in release builds as well, noticable with VSYNC ON or OFF

> In #88219#1312929, @PratikPB2123 wrote: > Can only reproduce on debug build. All release builds works fine here (2.92, 2.93.7, 3.2) > @lichtwerk , can you recheck? Getting this in release builds as well, noticable with VSYNC ON or OFF

Jeroen Bakker commented

2022-05-13 11:24:16 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2022-05-13 11:24:16 +02:00

Thanks, that is a strange one. The source points to a diff that is eevee internal. but the bug is also about workbench. I suspect that there is a different change happened, but the mentioned commit only exaggerate it. I'll build a similar configuration and see if I am able to point to a different cause.

Philipp Oeser commented

2022-05-13 11:57:50 +02:00

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-fedora-36-Rawhide 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44

So to be precise, this is what I am getting (I will take some time bisecting things as performance seems to have taken various hits...):
Will update this table as bisecting progresses.
The culprit for the regression in material/rendered between 2.92 and 2.93 I think we have already found in 267a9e14f5.

version	VSYNC	fps solid	fps material	fps rendered
2.92	off	230	80	61
2.93.9 (regression caused by `267a9e14f5`)	off	230	57	41
3.0.1 (regression caused by `03013d19d1`)	off	200	57	41
3.1.2 (regression caused by `d09b1d2759`)	off	110	57	41
3.2beta (regression caused by `80859a6cb2`)	off	107	54	37

``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-fedora-36-Rawhide 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 ``` So to be precise, this is what I am getting (I will take some time bisecting things as performance seems to have taken various hits...): Will update this table as bisecting progresses. The culprit for the regression in material/rendered between 2.92 and 2.93 I think we have already found in 267a9e14f5. | version | VSYNC | fps solid | fps material | fps rendered | | -- | -- | -- | -- | -- | | 2.92 | off | 230 | 80 | 61 | | 2.93.9 (regression caused by 267a9e14f5) | off | 230 | 57 | 41 | | 3.0.1 (regression caused by 03013d19d1) | off | 200 | 57 | 41 | | 3.1.2 (regression caused by d09b1d2759) | off | 110 | 57 | 41 | | 3.2beta (regression caused by 80859a6cb2) | off | 107 | 54 | 37 |

Philipp Oeser changed title from ~~2.92 to 3.0 - Massive drops in Animation playback (fps) in the viewport~~ to Massive drops in Animation playback (fps) in the viewport

2022-05-13 12:42:11 +02:00

Philipp Oeser commented

2022-05-13 12:42:11 +02:00

Added subscriber: @JacquesLucke

Philipp Oeser changed title from ~~Massive drops in Animation playback (fps) in the viewport~~ to Regression: Massive drops in Animation playback (fps) in the viewport

2022-05-13 15:21:56 +02:00

Philipp Oeser commented

2022-05-16 10:35:05 +02:00

Fleshing out something like #98100 (Monitor FPS playback regressions in time for workbench and eevee) and adding that to test should help prevent this in the future hopefully

Jeroen Bakker commented

2022-05-16 12:24:44 +02:00

On my system (Linux + GTX760 + 470 drivers) I got a different cause for the eevee regression.

ba75ea8012
6842c549bb

Looking at the code I would think 6842c549bb
is more likely to be the culprit.

On my system (Linux + GTX760 + 470 drivers) I got a different cause for the eevee regression. ba75ea8012 6842c549bb Looking at the code I would think 6842c549bb is more likely to be the culprit.

Jeroen Bakker commented

2022-05-16 13:38:00 +02:00

Looking at the current results there isn't a single commit that can be pointed out as the root cause. There are multiple commits that reduced the performance. Some are more visible depending on the actual platform you're using.

Eevee is always optimized to the latest generation GPUs. What also leads to performance regressions to previous generations as GPU architectures can be totally different between generations.

With the upcoming eevee-next I would not spend to much time on getting the FPS back to what it was as it would require re-development and could impact the quality or performance in different ways.

Thing we should learn from this task is that monitoring is very important. Will check to set something up here that would create those kind of reports #98100 (Monitor FPS playback regressions in time for workbench and eevee).

For now lowering this issue and set it to known issue.

A huge thanks to everyone involved!

Looking at the current results there isn't a single commit that can be pointed out as the root cause. There are multiple commits that reduced the performance. Some are more visible depending on the actual platform you're using. Eevee is always optimized to the latest generation GPUs. What also leads to performance regressions to previous generations as GPU architectures can be totally different between generations. With the upcoming eevee-next I would not spend to much time on getting the FPS back to what it was as it would require re-development and could impact the quality or performance in different ways. Thing we should learn from this task is that monitoring is very important. Will check to set something up here that would create those kind of reports #98100 (Monitor FPS playback regressions in time for workbench and eevee). For now lowering this issue and set it to known issue. A huge thanks to everyone involved!

Raimund Klink commented

2022-05-16 13:59:26 +02:00

Small question, is this only impacting the viewport, or is it affecting the rendering (to image files) as well?

Jeroen Bakker commented

2022-05-16 14:14:04 +02:00

During final rendering to images the slowdown isn't that noticeable as writing to file and color management would be much more of a performance bottleneck.

RedMser commented

2022-05-19 20:21:36 +02:00

Added subscriber: @RedMser

Jacob Merrill commented

2022-05-31 19:33:12 +02:00

Added subscriber: @JacobMerrill-1

Jacob Merrill commented

2022-05-31 19:33:12 +02:00

"we are a animation software that is terrible at the actual act of animation"

maybe we can work on this and not label it as a known issue* -

"we are a animation software that is terrible at the actual act of animation" - maybe we can work on this and not label it as a known issue* -

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression: Massive drops in Animation playback (fps) in the viewport #88219