Page MenuHome

Limit grab brush updates per second

Authored by Pablo Dobarro (pablodp606) on Tue, Aug 6, 6:32 PM.



When I talked to @Sebastian Parborg (zeddb), he said that the update rate of the grab brush was way too high and it is causing performance issues. I limited the updates per second with a timer and the performance increases drastically

Current master:

This patch:

The 0.07 value was obtained experimentally on my computer, but it is probably not optimal. I'm not sure if this is the right way to do this.

Diff Detail

rB Blender

Event Timeline

Awesome! I think this issue is also present with texture painting. That is with input devices with high polling rate (like 1000Hz mice), some operations are executed way to often and causes blender to slow down to a crawl.

I don't know if setting a timer would be the best solution though. Perhaps we could have a distance threshold instead? I don't really know what would be best to be honest.

I have compiled and tested on Linux.

This patch makes working in Linux more comfortable when the brush is not relatively big (or view very zoom out) with this problem in Linux:

But when the brush is very big, in Linux the lag in response is still very large, for example in this file:

So I guess that problem in Linux is not entirely related to this.

For a simple grab operation, we can update once per redraw. Transform operators work the same way. That is done by ignoring any INBETWEEN_MOUSEMOVE events, and only using MOUSEMOVE.

There may be other tools with issues like this, and I don't know off the top of my head how dynamic topology interacts with this. In general for something that draws a curve I'd expect the number of updates to be defined by distance and spacing. For airbrush-like behavior it makes sense to use a timer. In both cases it is possible in principle to keep the UI more responsive by letting the updates lag behind, and only doing updates for N milliseconds at a time before redrawing.

But the basic grab case does not need timers or distance as far as I know.

@Brecht Van Lommel (brecht) @Sebastian Parborg (zeddb) I'm testing it ignoring INBETWEEN_MOUSEMOVE events and it works perfectly. Dyntopo also works fine. How should we approach this? Should I just add specific code for the grab brush here until we find a more general solution?

could this type of interaction improve the situation with edit mode performance or is it a whole other system and therefore unrelated?

@Pablo Dobarro (pablodp606), I think this is the general solution, some tools just don't need all the inbetween mouse events. The paint stroke code has more checks for specific tools like paint_tool_require_location, we can do the same here. The implementation of these things could be improved with a bigger refactor, but it's not that much of a problem.

I guess add something like paint_tool_require_inbetween_mouse_events(). Rotate and Thumb tools need this as well.

@noki paike (amonpaike), this is unrelated to edit mode performance.

  • Revert "Limit grab brush updates per second"
  • Ignore INBETWEEN_MOUSEMOVE events on certain brush tools
YAFU (YAFU) added a comment.EditedWed, Aug 7, 2:48 AM

The latest version of the patch is almost solving the problem related to Grab brush that I showed in my previous message!
My question is whether this really solves that bug for Linux if this could be implemented for other brushes, or this helps in performance for Grab brush but the problem about Windows being faster than Linux still persists.

This revision is now accepted and ready to land.Mon, Aug 12, 10:17 AM