It does not look like a major speed up when developer himself write in the commit that he don’t perceive the improvement and that change is valid for a point size of 30 that we don"t really know to what it corresponds.
It is hard to make improvement on something that was not tested a lot, yet. It is easy to have modifier preview doing weird thing by changing way to draw background from Theme to Viewport. or Color Type from Material to Single.
I obtained this.
Good news for those concerned about editmode performance.
Brecht has opened a task which identifies the cause of the regressions and requests that they be fixed before the official release. Believe it or not, much of it is not related to the actual drawing code. https://developer.blender.org/T57936
Wow, just tried using dyntopo in wireframe mode… it slows down to a crawl. It’s alright though, I just wanted to see the subdivision size more clearly before starting to work, I’m not actually using wireframe mode to sculpt.
I knew about modeling performance, but that’s edit mode performing poorly, isn’t it ? Always been the culprit as far as I know ? Sculpting however… I guess a mesh changing topology 30 times a second must be hard to make smooth.
For some reason, today, after I updated now my performance while trying to sculpt has become nearly unusable. It was fine before I updated and nothing changed on my PC between then and now. Anyone else having a similar issue?
Edit mode performance has always been bad, yes, but not even remotely close to how awful it is now. With subsurfs in particular, it’s over 10 times slower.
Blender 2.79’s viewport code has its origins all the way back in the 1990’s. Most consumer PC’s back then only had a single thread (so multithreading would’ve made no sense).