Voronoi smooth f1 3d high CPU #91085

New Issue

Peter Boos · 2021-08-31T14:52:54+02:00

Peter Boos commented

2021-08-31 14:52:54 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 (i'm using CPU)

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-08-19 18:36, hash: 962153dbed
Worked: 2.93.0 Alpha, branch: master, commit date: 2021-04-03 16:32, hash: 8681504f06

Short description of error
[CPU to 90% with smooth 3d veranoi]

Exact steps for others to reproduce the error

While trying to make a soap bubbles shader I noted a huge impact on my CPU.
I eventually got it down to specific settings (the default settings, smooth F1).
I tested with another version of Blender and then the CPU did not spike.
I narrowed it down to just Voronoi, and it's not even with all combinations (but the others won't give me soap).
Some other combinations in this shader gave also high CPU but not all combinations.

I'm aware 3.0 is not yet released but i hope this bug posting will improve (maybe revert) some code that was added to the Voronoi texture generator.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 (i'm using CPU) **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-08-19 18:36, hash: `962153dbed` Worked: 2.93.0 Alpha, branch: master, commit date: 2021-04-03 16:32, hash: `8681504f06` **Short description of error** [CPU to 90% with smooth 3d veranoi] **Exact steps for others to reproduce the error** While trying to make a soap bubbles shader I noted a huge impact on my CPU. I eventually got it down to specific settings (the default settings, smooth F1). I tested with another version of Blender and then the CPU did not spike. I narrowed it down to just Voronoi, and it's not even with all combinations (but the others won't give me soap). Some other combinations in this shader gave also high CPU but not all combinations. I'm aware 3.0 is not yet released but i hope this bug posting will improve (maybe revert) some code that was added to the Voronoi texture generator.

Peter Boos commented

2021-08-31 14:52:54 +02:00

Added subscriber: @PeterBoos

Peter Boos commented

2021-08-31 14:54:09 +02:00

voronoi-bug.blend and here is file showing the bug in 3.0

[voronoi-bug.blend](https://archive.blender.org/developer/F10357606/voronoi-bug.blend) and here is file showing the bug in 3.0

Richard Antalik commented

2021-09-01 04:49:30 +02:00

Added subscribers: @PratikPB2123, @iss

Richard Antalik commented

2021-09-01 04:49:30 +02:00

Unfortunately I can't reproduce any difference between 3.0 and 2.93

@PratikPB2123 Can you reproduce?

Unfortunately I can't reproduce any difference between 3.0 and 2.93 @PratikPB2123 Can you reproduce?

Pratik Borhade commented

2021-09-01 07:55:59 +02:00

Hi @iss , no difference between 2.93LTS (2021-06-02) & 3.0.0 (bd67bf4d106e)

I have also checked with old 2.93 build de06cb8559. Still it shows almost same CPU usage (in task manager -> performance tab)

System Information

Graphics card : AMD Radeon(TM) 535 ATI Technologies .```

Hi @iss , no difference between 2.93LTS (2021-06-02) & 3.0.0 (`bd67bf4d106e`) I have also checked with old 2.93 build de06cb8559. Still it shows almost same CPU usage (in task manager -> performance tab) --- **System Information** ```Operating system : Windows-10-10.0.18362-SP0 64 Bits Graphics card : AMD Radeon(TM) 535 ATI Technologies .```

Richard Antalik commented

2021-09-02 04:12:09 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2021-09-02 04:12:09 +02:00

Really not sure what could cause this, but I don't think it's bug in Blender really.

@PeterBoos Can you click on File > Defaults > Load Factory Settings, open file voronoi-bug.blend and re-check if this issue happens? I am thinking some addon doing something strange, but even that is unlikely.

Really not sure what could cause this, but I don't think it's bug in Blender really. @PeterBoos Can you click on File > Defaults > Load Factory Settings, open file `voronoi-bug.blend` and re-check if this issue happens? I am thinking some addon doing something strange, but even that is unlikely.

Peter Boos commented

2021-09-04 00:34:51 +02:00

With factory settings it still happens.
I noticed in the viewport settings in the blend file, has to be set to rendered (ea cycles preview). (this wasnt the case for the voronoi-bug.blend files (sorry)
The varanoi must be connected on its color (yellow).
and it must be in cycles, Eevee doesnt have the problem.

Also my machine is CPU i dont have a good graphics card but i got decent cpu.

Not sure the cause, the older blender didnt show this behaviour (here the fans spin up), its over after the 32 samples are done, but for the older blender version the cpu doesnt spike.

With factory settings it still happens. I noticed in the viewport settings in the blend file, has to be set to rendered (ea cycles preview). (this wasnt the case for the voronoi-bug.blend files (sorry) The varanoi must be connected on its color (yellow). and it must be in cycles, Eevee doesnt have the problem. Also my machine is CPU i dont have a good graphics card but i got decent cpu. Not sure the cause, the older blender didnt show this behaviour (here the fans spin up), its over after the 32 samples are done, but for the older blender version the cpu doesnt spike.

Richard Antalik commented

2021-09-21 23:15:15 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Richard Antalik commented

2021-09-21 23:15:15 +02:00

Checking again, I can reproduce quite high CPU usage when I coved whole viewport with mesh surface, but that is to be expected I think. At least older versions do behave exactly same here.

In #91085#1215938, @PeterBoos wrote:
Not sure the cause, the older blender didnt show this behaviour (here the fans spin up), its over after the 32 samples are done, but for the older blender version the cpu doesnt spike.

Question is: is the performance better in newer version or is it the same? This could have been some optimization in cycles that uses CPU better. But again I don't see difference between 2.93 and 3.0.

Checking again, I can reproduce quite high CPU usage when I coved whole viewport with mesh surface, but that is to be expected I think. At least older versions do behave exactly same here. > In #91085#1215938, @PeterBoos wrote: > Not sure the cause, the older blender didnt show this behaviour (here the fans spin up), its over after the 32 samples are done, but for the older blender version the cpu doesnt spike. Question is: is the performance better in newer version or is it the same? This could have been some optimization in cycles that uses CPU better. But again I don't see difference between 2.93 and 3.0.

Richard Antalik commented

2021-09-21 23:23:41 +02:00

Also forgot to mention, that today cycles-x has landed in master so please check if you still have issues in latest alpha build from https://builder.blender.org/download/daily/

AFAIK it improves mainly GPU rendering but still give it a try.

Also forgot to mention, that today cycles-x has landed in master so please check if you still have issues in latest alpha build from https://builder.blender.org/download/daily/ AFAIK it improves mainly GPU rendering but still give it a try.

Peter Boos commented

2021-09-24 13:47:42 +02:00

Hm tested it again apperantly smoothed F1 varanoi is something CPU intensive. (ea something that can be put endless reays into or something like that. And since the alpha version uses pretty high render samples by default (like 1000 instead of 4 or so), this is i thnk what keeps it bussy.

The only thing strange to me here is that EEVEE shows smoothed F1 in flash.
So i think the smoothing itself shouldnt be delaying that much, a textured or a varanoi should be about the same. maybe its something that can looked at, but its possible to reduce.

Another side thing i wonder perhaps the CPU is now put better at work and thus spiking, instead of slower resolving the viewport, although then still why varanoi and the others less ?.

Hm tested it again apperantly smoothed F1 varanoi is something CPU intensive. (ea something that can be put endless reays into or something like that. And since the alpha version uses pretty high render samples by default (like 1000 instead of 4 or so), this is i thnk what keeps it bussy. The only thing strange to me here is that EEVEE shows smoothed F1 in flash. So i think the smoothing itself shouldnt be delaying that much, a textured or a varanoi should be about the same. maybe its something that can looked at, but its possible to reduce. Another side thing i wonder perhaps the CPU is now put better at work and thus spiking, instead of slower resolving the viewport, although then still why varanoi and the others less ?.

Richard Antalik commented

2021-09-24 20:58:31 +02:00

In #91085#1225344, @PeterBoos wrote:
The only thing strange to me here is that EEVEE shows smoothed F1 in flash.
So i think the smoothing itself shouldnt be delaying that much, a textured or a varanoi should be about the same. maybe its something that can looked at, but its possible to reduce.

Eevee is implemented with GPU shaders, so it can't really utilize CPU. Also eevee and cycles are fundamentally different engines.

Can you somehow test if with higher CPU usage you get faster render time? Perhaps render animation of 100 frames.

> In #91085#1225344, @PeterBoos wrote: > The only thing strange to me here is that EEVEE shows smoothed F1 in flash. > So i think the smoothing itself shouldnt be delaying that much, a textured or a varanoi should be about the same. maybe its something that can looked at, but its possible to reduce. Eevee is implemented with GPU shaders, so it can't really utilize CPU. Also eevee and cycles are fundamentally different engines. Can you somehow test if with higher CPU usage you get faster render time? Perhaps render animation of 100 frames.

Richard Antalik commented

2021-09-24 20:58:41 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Peter Boos commented

2021-09-25 01:36:44 +02:00

I know their diffrent engines, but the color math behind the nodes is most likely the same.
its viewport not about final renders.

I know their diffrent engines, but the color math behind the nodes is most likely the same. its viewport not about final renders.

Richard Antalik commented

2021-10-14 23:57:02 +02:00

Sorry for late response, Just to clarify, nodes themselves don't have builtin math, they only describe shading for render engine. Eevee does this on GPU, cycles can do it on GPU or CPU but in both cases math would be different to Eevee.

Also you mentioned, this happens only with rendered shading which is almost same as if you would render the image with F12 key. That's why I asked for performance comparison with cycles. Since you say this is regression, and I assume this may be improvement. And since I can't reproduce the issue, I have to rely on data provided by you.

Is this still an issue?

Sorry for late response, Just to clarify, nodes themselves don't have builtin math, they only describe shading for render engine. Eevee does this on GPU, cycles can do it on GPU or CPU but in both cases math would be different to Eevee. Also you mentioned, this happens only with rendered shading which is almost same as if you would render the image with F12 key. That's why I asked for performance comparison with cycles. Since you say this is regression, and I assume this may be improvement. And since I can't reproduce the issue, I have to rely on data provided by you. Is this still an issue?

Raimund Klink commented

2021-11-04 11:53:23 +01:00

Added subscriber: @Raimund58

Raimund Klink commented

2021-11-04 11:53:23 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Raimund Klink closed this issue

2021-11-04 11:53:23 +01:00

Raimund Klink commented

2021-11-04 11:53:23 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

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

Voronoi smooth f1 3d high CPU #91085