Help me please. #82515

New Issue

Vladimir · 2020-11-08T23:48:37+01:00

Vladimir commented

2020-11-08 23:48:37 +01:00

Hello!
I suddenly found out that the blender does not know how to work with multithreading.
Really in 2k20?
This makes it very slow. The use of one even non-demanding function can take 10-15 minutes,and only one CPU core is involved, with a face count of ~16 million per mesh .
Is it possible to use more cpu cores?
Thx.
Запись экрана_20201109_043754.mp4

Hello! I suddenly found out that the blender does not know how to work with multithreading. Really in 2k20? This makes it very slow. The use of one even non-demanding function can take 10-15 minutes,and only one CPU core is involved, with a face count of ~16 million per mesh . Is it possible to use more cpu cores? Thx. [Запись экрана_20201109_043754.mp4](https://archive.blender.org/developer/F9241264/Запись_экрана_20201109_043754.mp4)

Vladimir commented

2020-11-08 23:48:37 +01:00

Added subscriber: @Vladimir-21

Vladimir changed title from ~~Hello!~~ to Help me please.

2020-11-08 23:50:41 +01:00

Robert Guetzkow commented

2020-11-09 09:44:23 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-11-09 09:44:23 +01:00

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

Robert Guetzkow closed this issue

2020-11-09 09:44:23 +01:00

Robert Guetzkow self-assigned this 2020-11-09 09:44:23 +01:00

Robert Guetzkow commented

2020-11-09 09:44:23 +01:00

You're using Voxel Remeshing at an incredibly high level of detail which is a computationally expensive and memory intensive algorithm. In fact, due to the extremely small voxel size you've chosen your memory consumption is rising and your system is close to running out of memory. The operation is expected to take a while and Blender does use multithreading were possible. While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.

Vladimir commented

2020-11-09 19:19:51 +01:00

In #82515#1050411, @rjg wrote:
You're using Voxel Remeshing at an incredibly high level of detail which is a computationally expensive and memory intensive algorithm. In fact, due to the extremely small voxel size you've chosen your memory consumption is rising and your system is close to running out of memory.

Hello, That yes,but What does the consumed memory have to do with it? I didn’t show it.
All functions are executed only on one core. Take the operation CTRL+Z or modifiers, any drop-down menus work very slowly because of this, and so on.
Maybe there is an opportunity as in the settings to switch a multithread? or are there other possible options?

here is another example
Запись экрана_20201108_004141.mp4
I'm not asking for something extraordinary. I don't ask why the blender doesn't have a Zbrush level or something.I just think that support for multithreading on basic functions should be, or am I wrong?

Although I have an idea how to bring the blender closer to the Zbrush level.But alas, I'm not a programmer and I can't implement this in code. I thing, it's all about the method of rendering the viewport.But I can draw it :)
I tried to outline everything in the screenshot below

Is it possible, or is it dumb?

> In #82515#1050411, @rjg wrote: > You're using Voxel Remeshing at an incredibly high level of detail which is a computationally expensive and memory intensive algorithm. In fact, due to the extremely small voxel size you've chosen your memory consumption is rising and your system is close to running out of memory. Hello, That yes,but What does the consumed memory have to do with it? I didn’t show it. All functions are executed only on one core. Take the operation CTRL+Z or modifiers, any drop-down menus work very slowly because of this, and so on. Maybe there is an opportunity as in the settings to switch a multithread? or are there other possible options? here is another example [Запись экрана_20201108_004141.mp4](https://archive.blender.org/developer/F9246300/Запись_экрана_20201108_004141.mp4) I'm not asking for something extraordinary. I don't ask why the blender doesn't have a Zbrush level or something.I just think that support for multithreading on basic functions should be, or am I wrong? Although I have an idea how to bring the blender closer to the Zbrush level.But alas, I'm not a programmer and I can't implement this in code. I thing, it's all about the method of rendering the viewport.But I can draw it :) I tried to outline everything in the screenshot below ![1.png](https://archive.blender.org/developer/F9247128/1.png) Is it possible, or is it dumb? ``` ```

Robert Guetzkow commented

2020-11-09 19:48:46 +01:00

In #82515#1050998, @Vladimir-21 wrote:
Hello, That yes,but What does the consumed memory have to do with it? I didn’t show it.

You showed the task manager, which also displays the memory consumption. It peaked at about 30 GB.

All functions are executed only on one core. Take the operation CTRL+Z or modifiers, any drop-down menus work very slowly because of this, and so on.
Maybe there is an opportunity as in the settings to switch a multithread? or are there other possible options?

here is another example

Your example video clearly shows that all your processor cores are used, so evidently Blender uses multithreading. The reason for Blender freezing is most likely that you're working on a mesh with over 17 million faces, which is quite a lot. In your first example Blender also seems to have utilized multiple cores, up until large amounts of memory had to be allocated for the voxel remeshing.

While there may be opportunities to optimize code and improve performance, these cases are not handled as bug reports. For feedback and improvements suggestions you can create a post on the websites listed here . If you're interested about the current performance improvements that are in development for sculpting, take a look at #81180.

> In #82515#1050998, @Vladimir-21 wrote: > Hello, That yes,but What does the consumed memory have to do with it? I didn’t show it. You showed the task manager, which also displays the memory consumption. It peaked at about 30 GB. > All functions are executed only on one core. Take the operation CTRL+Z or modifiers, any drop-down menus work very slowly because of this, and so on. > Maybe there is an opportunity as in the settings to switch a multithread? or are there other possible options? > > here is another example Your example video clearly shows that all your processor cores are used, so evidently Blender uses multithreading. The reason for Blender freezing is most likely that you're working on a mesh with over 17 million faces, which is quite a lot. In your first example Blender also seems to have utilized multiple cores, up until large amounts of memory had to be allocated for the voxel remeshing. While there may be opportunities to optimize code and improve performance, these cases are not handled as bug reports. For feedback and improvements suggestions you can create a post on the websites listed [here ](https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests). If you're interested about the current performance improvements that are in development for sculpting, take a look at #81180.

Vladimir commented

2020-11-09 21:16:11 +01:00

3: 08 are all cores used here? If so, this operation was directly related to the sculpt mode (smooth mask). Everything is fine with multithreading here. But we are talking about basic functions that were shown before :)))
If you pay attention, the percentage of CPU usage is always around ~10, almost all the time.Which is equivalent to only loading one core, and the program hangs. From which we can conclude that blender does not know how to work fully with multithreading.
Please try to do the same,and you will see for yourself ;)

3: 08 are all cores used here? If so, this operation was directly related to the sculpt mode (smooth mask). Everything is fine with multithreading here. But we are talking about basic functions that were shown before :))) If you pay attention, the percentage of CPU usage is always around ~10, almost all the time.Which is equivalent to only loading one core, and the program hangs. From which we can conclude that blender does not know how to work fully with multithreading. Please try to do the same,and you will see for yourself ;)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Help me please. #82515