On 3/28/22 2:53 AM, mark_at_yahoo via Rosegarden-devel wrote:
On 3/27/22 4:17 PM, Ted Felix wrote:
Should be something of a performance bump. Please test latest git.
I tried the change (in the context of my branch's HEAD) and didn't see
much difference, either positive or negative. Maybe what I test isn't
hitting the palette code. Regardless, in my opinion the new version is
indisputably more correct.
Yeah. I noticed little improvement myself. Usually QSettings
absolutely destroys performance. We would have noticed it earlier if it
were being hit really frequently.
The real issues are in the drawing code. Both the Segment Canvas
(CompositionView which is where I have focused my efforts) and likely
the editors. I usually monitor cpu usage closely with "top" or some
other tool while running an unoptimized debug build on an old anemic
machine. (I'm currently using a 10-year-old Core i3, and it's still too
fast for my tastes.) Then I remove pieces to see which one is the
culprit. I've found this approach to be much more reliable than profilers.
Some of the history and current status of performance in Rosegarden
is covered in bug #1391:
https://sourceforge.net/p/rosegarden/bugs/1391/
Ted.
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
