Self-built developments builds running under the debugger run very slowly
(I'm on Windows 7).  I know performance degrades as your scores get larger,
but it seems this is significantly worse in the development builds.  As a
point of reference, I have a 20-page big band score that in 1.3 is still
virtually instantaneous in responding to change, but in 2.0 it takes around
5 seconds to response to each note edit - and that's if I have *not*
generated parts (see below).  This is not an outlying example - that's about
the ratio I see for all scores.  But then, dialogs are also very slow to
respond even for small scores, making me hope it's just the nature of a
debug builds.

I guess this has been true for me all along but I rarely was loading
anything but small examples.  So far I've just accepted it and hoped it was
*because* it was a development build running under debugger and that a
regular install build would be better.  It takes too long for me to do
another complete build to want to test this theory.  Can anyone comment?

I know that major layout optimizations (eg, not laying out the entire score
every edit) are not planned for this release, but I hope we are not
regressing too much.  I seem to have noticed that sometimes there are
multiple layout() calls for each edit operation and wonder if some of these
might be unnecessary?

Also, I wonder about linked parts.  Is it necessary to layout each part
after a modification to the score?  My big band score has a part for each
instrument.  With no parts, it's around 5 seconds per edit.  With all parts
generated, it's over twice that.  I'm guessing *all* parts are being laid
out anew with each score edit.  I wonder if we could perhaps skip layout for
parts not in an active view (eg, not displaying in another part of a split
screen), instead marking them dirty and only doing the layout when they come
into view?  That might be an easy enhancement.




--
View this message in context: 
http://dev-list.musescore.org/Performance-tp7578578.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to