Mesh modeling performance regressions #57936

New Issue

List of performance issues that we would like to fix or investigate for 2.80:

Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here.
BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance.
Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs)
Manipulate modal callback performance may be problematic: #55458

List of performance issues that we would like to fix or investigate for 2.80: * Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here. * BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance. * Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs) * Manipulate modal callback performance may be problematic: #55458

Added subscriber: @brecht

#67972 was marked as duplicate of this issue

#54702 was marked as duplicate of this issue

Added subscriber: @KINjO

Added subscriber: @rdnmnm

This comment was removed by @rdnmnm

*This comment was removed by @rdnmnm*

Added subscriber: @ostry

Added subscriber: @ixd

Added subscriber: @zappedfish

Added subscriber: @kioku

Added subscriber: @Stefan_Werner

Added subscriber: @lastrodamo

Added subscriber: @Regnas

Funny, turning off overlays increases performance in edit mode a little bit, why is that?

Because there's fewer things to draw then, that's expected.

Added subscriber: @RainerTrummer

Added subscriber: @lemenicier_julien

Added subscriber: @oenvoyage

Added subscriber: @0o00o0oo

Added subscriber: @MeshVoid

Added subscriber: @VladimirTurcan

Added subscriber: @LucasVeber

Added subscriber: @zhanghua

Looked into Custom Data layers.

Layers which are dependent on am modifier stack (like deform groups) are not preserved if they are not needed. So this part is good.

However, the UVs and vertex colors are always preserved. This is actually the same in Blender 2.7, so i see potential being more memory efficient than 2.7.

Looked into Custom Data layers. Layers which are dependent on am modifier stack (like deform groups) are not preserved if they are not needed. So this part is good. However, the UVs and vertex colors are always preserved. This is actually the same in Blender 2.7, so i see potential being more memory efficient than 2.7.

Added subscriber: @ArtemBataev

Added subscriber: @R_dva

Added subscriber: @JonDoe286

Added subscriber: @heini

Added subscriber: @TodorNikolov

Added subscriber: @Ace_Dragon

Hi.

Is there any reason for the decision to not fix these regressions for the 2.8 final release? Unless the solutions are more complex than we users think they are, it seems like an unforced error that really dampens what would otherwise be a truly major milestone.

Hi. Is there any reason for the decision to not fix these regressions for the 2.8 final release? Unless the solutions are more complex than we users think they are, it seems like an unforced error that really dampens what would otherwise be a truly major milestone.

Further performance improvements are more complex than you think, that's exactly the reason they will be for later releases.

Added subscriber: @SergienkoEugene

Added subscriber: @AndreyRusnak

Added subscriber: @machieb

I´ve tested the different render possibilities in blender and compared blender 2.79b with blender 2.80 5f140e61c2.
It´s the same scene in blender 2.79b and blender 2.80.

Blender 2.79b

CPU(AMD Threadripper 1950X 16Cores)
bmw27_cpu.blend (tiles 32x32) 01:20.53
bmw27_cpu_denoise.blend (tiles 32x32)01:24.32
2xGPU (Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB)
bmw27_gpu.blend (tiles 240x180) 01:09.15
bmw27_gpu_denoise.blend (tiles 240x180) with denoise 01:12.15
GPU (Geforce Gtx 1080 Ti 11GB)
bmw27_gpu.blend (tiles 240x180) 02:01.35
bmw27_gpu_denoise.blend (tiles 240x180) with denoise 02:05.07

Blender 2.805f140e61c2CPU (AMD Threadripper 1950X 16Cores)
bmw27_cpu.blend (tiles 32x32) 01:46.65
bmw27_cpu_denoise.blend (tiles 32x32) 01:51.20
2xGPU (Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB)
bmw28_gpu.blend (tiles 32x32) 00:34.24
bmw28_gpu_denoise.blend (tiles 32x32) with denoise 00:40.69
GPU (Geforce Gtx 1080 Ti 11GB)
bmw27_gpu.blend (tiles 32x32) 00:49.69
bmw27_gpu.blend (tiles 32x32) with denoise 00:55.06
CPU+GPU (AMD Threadripper 1950X 16Cores + Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB)
bmw28_gpu_cpu.blend (tiles 16x16) 00:30.40
bmw28_gpu_cpu_denoise.blend (tiles 16x16) with denoise 00:39.05

Summing up blender 2.79b renders the scene on cpu ca. 25% faster. Why?Compared one GPU to two GPUs inblender 2.79bthere is a75% boost with two GPUs.
In blender 2.80 the boost is low, only 44%. Why, what is slowing down the second GPU? Blender 2.8 is also using a newer CUDA version.
GPU rendering in blender 2.80 is more than twice as fast as in blender 2.79b!
I couldn´t find any significant slowdown with denoise.

I´ve tested the different render possibilities in blender and compared blender 2.79b with blender 2.80 5f140e61c28c. It´s the same scene in blender 2.79b and blender 2.80. **`Blender 2.79b`** **CPU**(AMD Threadripper 1950X 16Cores) bmw27_cpu.blend (tiles 32x32) **01:20.53** bmw27_cpu_denoise.blend (tiles 32x32)**01:24.32** **2xGPU** (Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB) bmw27_gpu.blend (tiles 240x180) **01:09.15** bmw27_gpu_denoise.blend (tiles 240x180) with denoise **01:12.15** **GPU** (Geforce Gtx 1080 Ti 11GB) bmw27_gpu.blend (tiles 240x180) **02:01.35** bmw27_gpu_denoise.blend (tiles 240x180) with denoise **02:05.07** **`Blender 2.80`**5f140e61c28c**CPU** (AMD Threadripper 1950X 16Cores) bmw27_cpu.blend (tiles 32x32) **01:46.65** bmw27_cpu_denoise.blend (tiles 32x32) **01:51.20** **2xGPU** (Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB) bmw28_gpu.blend (tiles 32x32) **00:34.24** bmw28_gpu_denoise.blend (tiles 32x32) with denoise **00:40.69** **GPU** (Geforce Gtx 1080 Ti 11GB) bmw27_gpu.blend (tiles 32x32) **00:49.69** bmw27_gpu.blend (tiles 32x32) with denoise **00:55.06** **CPU+GPU** (AMD Threadripper 1950X 16Cores + Geforce Gtx 1080 Ti 11GB / Geforce Titan X 12GB) bmw28_gpu_cpu.blend (tiles 16x16) **00:30.40** bmw28_gpu_cpu_denoise.blend (tiles 16x16) with denoise **00:39.05** Summing up **blender 2.79b renders the scene on cpu ca. 25% faster**. **`Why?`**Compared one GPU to two GPUs in**blender 2.79b**there is a**75% boost** with two GPUs. In **blender 2.80** the boost is **low, only 44%**. Why, what is slowing down the second GPU? Blender 2.8 is also using a newer CUDA version. GPU rendering in blender 2.80 is more **than twice as fast** as in blender 2.79b! I couldn´t find any significant slowdown with denoise.

Added subscriber: @Yikes

Added subscriber: @howardt

Added subscriber: @xdanic

Added subscriber: @pabcou

Added subscriber: @nokipaike

here is another bizarre and interesting phenomenon …
the first ship is composed of many objects but all edited simultaneously … the second ship is a single object …
notice the differences …

here is another bizarre and interesting phenomenon … the first ship is composed of many objects but all edited simultaneously … the second ship is a single object … notice the differences … ![confronto.gif](https://archive.blender.org/developer/F7670985/confronto.gif)

Added subscriber: @filibis

Added subscriber: @zebus3dream

Added subscriber: @AlbertoVelazquez

Added subscriber: @finnb

In #57936#755441, @nokipaike wrote:
here is another bizarre and interesting phenomenon …
the first ship is composed of many objects but all edited simultaneously … the second ship is a single object …
notice the differences …

Looks like you have proportional editing turned on, which doesn't apply between objects even if they are edited simultaneously. The additional calculation of proportional editing for the entire ship vs. one part could be slowing it down.

> In #57936#755441, @nokipaike wrote: > here is another bizarre and interesting phenomenon … > the first ship is composed of many objects but all edited simultaneously … the second ship is a single object … > notice the differences … > ![confronto.gif](https://archive.blender.org/developer/F7670985/confronto.gif) Looks like you have proportional editing turned on, which doesn't apply between objects even if they are edited simultaneously. The additional calculation of proportional editing for the entire ship vs. one part could be slowing it down.

In #57936#767606, @finnb wrote:
Looks like you have proportional editing turned on, which doesn't apply between objects even if they are edited simultaneously. The additional calculation of proportional editing for the entire ship vs. one part could be slowing it down.

It was a test to make bottlenecks more evident on how a single object with a high number of polygons is currently structured.
Proportional editing turned on has nothing to do with it, it is enabled to make this slow down clear compared to when multiple objects are being edited simultaneously.

it is a test done on purpose to perhaps inspire some enlightening mind that can find a solution.

> In #57936#767606, @finnb wrote: > Looks like you have proportional editing turned on, which doesn't apply between objects even if they are edited simultaneously. The additional calculation of proportional editing for the entire ship vs. one part could be slowing it down. It was a test to make bottlenecks more evident on how a single object with a high number of polygons is currently structured. Proportional editing turned on has nothing to do with it, it is enabled to make this slow down clear compared to when multiple objects are being edited simultaneously. it is a test done on purpose to perhaps inspire some enlightening mind that can find a solution.

Removed subscriber: @lastrodamo

Added subscriber: @Dspazio

Added subscriber: @Lambdadelta

Added subscriber: @MaciejJutrzenka

Added subscriber: @BartekMoniewski

Added subscriber: @SamGreen

Added subscriber: @Sergey

Un-assigning.

There are other developers active looking into this and related projects. Happy to help with anything, but would need to know where the latest development brought us forward.

Un-assigning. There are other developers active looking into this and related projects. Happy to help with anything, but would need to know where the latest development brought us forward.

Added subscriber: @Lolme3

Added subscriber: @Nominous

Removed subscriber: @machieb

Added subscriber: @Orange3d

Added subscriber: @RedMser

Added subscriber: @Vyach

Added subscriber: @ckohl_art

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Mesh modeling performance regressions #57936