diff options
| author | Germano Cavalcante <germano.costa@ig.com.br> | 2021-06-10 17:13:01 +0300 |
|---|---|---|
| committer | Germano Cavalcante <germano.costa@ig.com.br> | 2021-06-11 16:49:50 +0300 |
| commit | 0eb9351296dbed5e7ac10ca56132d5e51e5f388d (patch) | |
| tree | 48de5ef4538c9346d1cc9130ffe50ee8c052fc32 /source/blender/editors/screen/screen_ops.c | |
| parent | 2330cec2c6a7632459c21f51723497e349a042bf (diff) | |
Refactor: use 'BLI_task_parallel_range' in Draw Cache
One drawback to trying to predict the number of threads that will be
used in the `task_graph` is that we are only sure of the number when the
threads are running.
Using `BLI_task_parallel_range` allows the driver to
choose the best thread distribution through `parallel_reduce`.
The benefit is most evident on hardware with fewer cores.
This is the result on an 4-core laptop:
||before:|after:
|---|---|---|
|large_mesh_editing:|Average: 5.203638 FPS|Average: 5.398925 FPS
||rdata 15ms iter 43ms (frame 193ms)|rdata 14ms iter 36ms (frame 187ms)
Differential Revision: https://developer.blender.org/D11558
Diffstat (limited to 'source/blender/editors/screen/screen_ops.c')
0 files changed, 0 insertions, 0 deletions