Thanks for the response. My system has two SSDs (1GB and 512GB). Both are fairly new, but I don’t know if they are NVMe drives.
Thanks for the response. I did have condensing enabled, but I’m relatively certain that I’ve seen performance issues with it turned off. I’ll leave it off for a while to see what happens.
There are many variables as to how Dorico will perform on a given system, but for a very rough rule of thumb, something like the Geekbench multi-core score should give a reasonable indication of perceived performance on larger projects. For instance compare your laptop and desktop:
- https://browser.geekbench.com/v5/cpu/696999 - single core: 908, multi-core: 1174
- https://browser.geekbench.com/v5/cpu/764580 - single core: 950, multi-core 6614
Although there’s only a modest increment in the single core performance, the multi-core performance is 5-6 times higher. I’m sure the SSD speed is a factor in general performance improvements, but during regular score editing, Dorico will barely touch the disk, as it’s CPU-bound, rather than I/O-bound, so I’ll be very surprised if it makes any difference.
Intel Core i7 3770, peaks at 3.7GHz
4 physical cores, 8 logical processors
I’ll fall back on what I said earlier about other products being able to handle the same score with much greater ease. Yes, Dorico 3 is perhaps more advanced than some of the other products, but I would not expect there to be such a huge difference. I’m hoping that disabling condensing will make an improvement, as someone suggested.
Those programs aren’t condensing…
If you switch condensing off and Dorico 3 has significantly worse performance than Dorico 2, that would suggest there is something going on that is specific to your score, which the Steinberg team would probably be interested in investigating.
You can still run Dorico 2 with your Dorico 3 licence if you want to do a direct comparison, but you have to close one version before you load the other one.
Thanks for the response. I know my processor is several generations behind, but I had not considered benchmarking it. The results are interesting. https://browser.geekbench.com/v5/cpu/765463 (784 / 2988). Probably time for an upgrade for sure, but still it seems like there shouldn’t be such a huge impact. If the base specs should be higher then someone needs to officially publish those, even recommending a minimum benchmark score.
We cannot help you without the information that Daniel asked for: the diagnostic report and a project that is slow for you. Dorico has to do a huge amount of calculation - probably an order of magnitude more than older generation applications - in order to do the complex processing for collision avoidance, condensing and all the other features that are intended to reduce the amount of time the user has to spend tidying up the score. So it’s not particularly meaningful to compare the performance of Dorico with other applications.
However, we would usually expect performance on a moderate size score to be much better than you are reporting (there are many users who are editing larger scores without problems), so this suggest that there’s a specific problem with either your system or your project. There are number of known issues that we may spot straight away, or there may be some new performance problem that we haven’t yet encountered. We’re unable to tell without the project and the diagnostics.
Understood. I’m going to try working with it off for a while. Now that I think about it, the time delay when enabling/disabling condensing is very close to what I’m observing for individual edits once the score has condensing enabled. So there’s probably something to that.
TBH, if condensing imposes such significant overhead then it should be turned off (including recalculation) when I’m in Galley view. I’d rather pay that penalty when I switch to page view rather than incrementally throughout an editing session, especially since you can’t edit with condensing turned on (in Page view mode). It’s clearly intended to help readability of a score in playback (and print) mode, but if I’m editing I would not expect to have to bear the burden of keeping condensing in sync in the background. IOW, Write mode is not really write mode if I’m in page view and have condensing turned on.
I understand. I’ve been trying to generate the diagnostics report, but when I select that option in the menu nothing happens. Does it get generated silently and if so where is the file stored?
It should land on your desktop automatically, and yes, it’s created silently.
On this subject, since the order of magnitude of computing is so drastically different from its competitors, perhaps it would be useful to make a sticky post in this forum detailing this in full and some of the most common issues and tips for maximizing performance.
Whenever I see a performance problem, I wonder if removing the video dll would help the performance problem (at least somewhat).
Color me dubious. From my measurements Dorico doesn’t touch the disk at all. What you are observing is frankly impossible.
Dr Paul’s Geekbench scores put this one to bed, didn’t they?
I wonder if you have a variety of third-party VST plug-ins that might be slowing things down? That’s been shown to be a problem in other threads.
I’m experiencing similar problems in Dorico 3 with a score that I’ve written with Sibelius a few years ago. I imported it into Dorico via MusicXML. Editing actually is somewhat painful. As lje67 pointed out it’s not that it would be unusable, but a lot of operations have a varying latency between 100-700 milliseconds. I’m on a highly overclocked quadcore i7 here with a good amount of RAM and a SSD harddrive. What can I do to improve performance?
Here is my geekbench result: https://browser.geekbench.com/geekbench3/8839799
Welcome to the forum, jasal82. Your best bet is to provide the project itself, along with specific details of which operations in particular you find slow (e.g. a description like “I open the full score layout, I select the first note in the violin 1 part in bar 83, I start note input and type C D E F, and it takes 2 seconds to input each note”). You can either attach the project here, or you can email it to me at d dot spreadbury at steinberg dot de.
Experiencing similar problems with the Dorico 3 trial on my:
late 2013 Mac Pro (trashcan) 2.7 GHz 12 Core Xeon E5-2697v2, 64ram, SSD.
(no problems whatsoever with Sibelius Ultimate 2020.1)
Condensing is turned off.
Look forward to any updates/solutions on this thread!