So, did some quick test:
Add action (brand new): Unbelievably faster now. Near instant in one of my test CAPX's now.
Edit Action (existing): Much faster. On one of my test machine's (the same one I ran the fresh install test on in the previous page), the same one that reported about 1.5-1.8s is now taking ~0.5-1s. This is a huge improvement.
I did notice *some* actions are faster to edit than others. When editing a function action, it is noticeably faster than editing an action that was setting layers opac.
I then tried r251 on my more powerful machine. It is pretty much on par with my W7 machine. The W7 machine is an old laggy machine, but still out beats my 6700k beast. But, in comparison to speed previously witnessed this is a huge step forward. I would say the speed is within acceptable ranges now
Again, I have not done heavy testing yet. But these initial results are amazing.
Windows Update / Meltdown
It is worth noting, this issue was not caused by a windows update, or meltdown. For several reasons (not that it is too important, but to keep facts straight and prevent going down rabbit holes):
- The bug was shown on both AMD and Intel (there is meltdown and specter. one of them effects only Intel, the other is both AMD and Intel).
- This bug pre-dates meltdown updates, and was also tested on pre-meltdown updated machines
- a user actually reported better performance after the meltdown update
- it was shown early W10 had the issue (it has been there since the beginning of W10).
- Similar bugs were reported months and even over a year ago, showing this is not related to a recent update
- ...there are plenty of other test and benchmarks that could be run around Windows Update, but I don't believe they are too important given the vast amount of information already collected (and given the improvements with r251)
It is completely reasonable to assume (and probably did), updates may have caused the issue to get worse and better over time (one update makes it worse, the next better, and so forth). But, it would be incorrect to say without a doubt windows update or meltdown caused this bug when you look at all data at hand. It would be safer to say, this has existed since W10 was officially released (which has been confirmed through testing). Again, not too important, but it should be said to prevent people from going down the wrong rabbit hole.
A side note, there are still other issues in the performance that users have reported, such as slow image loader. I have done my best to keep those out of here and stay focused on the issue I reported which was slow dialogs mainly with adding/editing actions. My hope was they were related, but this fix did not fix the other issues. Unfortunately, the users affected by other slowdowns will need to create a new bug report. This one has worn me down, I rather not pursue the other issues at this point (and to be honest, the other issues do not affect me as much). I will, however, help anyone with testing that does try to pursue the other issues as it is the right thing to do (as so many have helped me with this issue).
All-in-all, initial results are great. One could say the difference is beyond great, it is fantastic.
I am quite happy with the performance right now. Others are still affected by similar issues but, if we look back at the original bug report, so far it is much better. I am going to plug away and see how it goes over the next week.
It took a lot of effort on both sides Ashley (there were plenty headaches on both sides). Ultimately, you came through and I am very happy with this release. I also recognize and appreciate the effort you have put into this at the end.
I would also thank everyone who helped test out this bug. This would have been impossible to fix without all of your help.
And with that...Program on folks!!
Edit: fixed broken list