From 7471f09f2bb20fed33c57ca0ad53990be3eb48fd Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Mon, 5 Dec 2016 16:31:34 +0100 Subject: Depsgraph: Use HIGH priority for scheduled tasks This kind of keeps threads "warmer" and should in theory give better cache coherency bringing some %% of speedup. It was already tested few months ago and it gave few % speedup in barber shop, but was reverted due to some bone popping. The popping is now fixed so it should be fine to use new scheduling policy. --- source/blender/depsgraph/intern/eval/deg_eval.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source/blender/depsgraph/intern/eval/deg_eval.cc') diff --git a/source/blender/depsgraph/intern/eval/deg_eval.cc b/source/blender/depsgraph/intern/eval/deg_eval.cc index e926f83bcbe..065f65659e6 100644 --- a/source/blender/depsgraph/intern/eval/deg_eval.cc +++ b/source/blender/depsgraph/intern/eval/deg_eval.cc @@ -304,7 +304,7 @@ static void schedule_node(TaskPool *pool, Depsgraph *graph, unsigned int layers, deg_task_run_func, node, false, - TASK_PRIORITY_LOW, + TASK_PRIORITY_HIGH, thread_id); } } -- cgit v1.2.3