ON1 2019.1 speed improvement encountered by some anti-virus and anti-malware adjustments
I made some additional adjustments to the exclusion list that my antivirus and anti-malware use. Up until today I had only excluded the directories containing images that where used in my catalog. Today, I went one step further and it has seemed to help a lot. By a lot, I mean, much more responsive especially while editing and using sliders.
I excluded the appdata directory for ON1 for both products. On a Windows machine that directory is:
C:\Users\Kevin\AppData\Roaming\ON1 (replace Kevin with your username)
I also excluded the directories that are used by ON1 for the Scratch folder and the Browse cache. These are set inside of ON1 under preferences. I had already moved these folders to their own SSDs a few months back.
My impression is that the database files that ON1 seems to want to beat to death with updates (or whatever) are in the appdata\Roaming\ON1 somewhere and excluding this directory tree is the main improvement.
I just finished editing a photo that has 10 filters. I even have the left pane open and LUTs Filter panel open. I know that panel is updating faster then it was yesterday. The LUT panel stutters a little bit, but nothing like yesterday and while it is repainting the individual LUTs to match the image I am working on, I can move a slider on any other filter in the Effects tab and get immediate results. Yesterday, 5 or 6 filters where causing me excessive slowness and lagging of the slider with the Levels and image changes. I understand that the filters themselves might be more or less intensive, but still....
It is worth a check for everyone, IMO.
+1 to Kevin!
I tried what you said and saw immediate improvement. This is an outstanding find. I also added the following file types to the exclude list: NEF, TIF, TIFF, JPG, On1., and cube, but did not see much improvement. I think Kevin is spot-on with the appdata/On1 and scratch folder guidance.
Thank-you for sharing this improvement.0
Glad to be able to help. I just submitted a bug ticket with a link to this post so ON1 tech support will at least be able to check it out.0
+3 to Kevin :-)
I had forgotten of this fix and had to update my old ON2018 references. Now ON1 19.1 is very responsive again :-)
Best Xmas present so far ;-)0
Hi, what does moving the Scratch folder and the Browse cache to an external hard-drive actually do or accomplish?
I have excluded all of ON1 from my virus program.....0
I have done the same with my Norton but I don't think this is going to solve On1's conflict with my graphics driver0
Imagine 12 or more people trying to remove or put dishes into your dishwasher all at the same time. Pretty much any folder on the system drive will be treated like this. If the scratch drive is on the system disk, then ON1 will be accessing it. The operating system will be accessing some other folder(s) on the system disk, and probably at least two dozen other programs running in the background will also be accessing some file(s) or folder(s) also on the system disk. None of them are accessing the same things, but they are all telling the system drive to do something. The drive has to multi-task and keep them all happy. No matter how many cores you have on the processor, the bottle neck becomes the drive itself. SSD drives are much faster then RPM (spinner) drives, but even SSD drives have to multi-task. So by moving the scratch and browse folders (or making sure they are not on the system drive) is just one more thing to help ON1 run as fast as it can.0
Charles, I agree on the graphics driver issue.0
Thanks Kevin, I just have a 1T WD spinner external drive, would moving these files to this type of drive improve ON1's performance even though it is not an SSD drive?0
I looking at where 2019 has my scratch folder and it says its using 2018 folder instead of the 2019 folder. I still have 2018 installed not sure if that makes any difference but I'm willing to move to an extra internal disk0
Jim, I think moving the cache and browse folders provides minimal improvement. I would leave them alone for now. The only reason I moved mine was because I had a bunch of 500GB SSD drive and a tower case so it was painless and free (basically).
Charles, my comments to Jim also apply to you. I think that moving either the ON1 scratch or cache would probably not even be noticeable.
The exclusion of the appdata ON1 subdirectory is what I believe helped the most. And what I saw was big improvements in browsing and in editing with filter responsiveness. ON1 support is looking into it and has asked me for more data. Graphics drivers and crashes are probably not going to be impacted by any new exclusions. The exclusions are really for the anti-virus and anti-malware software, telling the anti-xxx software to keep it's nose out of these paths (directories). The anti-xxx software monitors everything that is not excluded and any small change or file creation/deletion is checked and validated. That just adds more work for the hard drive and slows down every piece of software that is using whatever the anti-xxx software is monitoring.
Using anti-xxx software has always been a trade-off. You get protection, but you give up a bit of performance. With faster processors and hard drives, the performance hit goes down, but it is still there. What I think is happening (just a guess) is that ON1 PR 2019 is doing a LOT of tiny modification to one of it's data bases which is located in the appdata ON1 directory tree. This in turn, causes the anti-xxx software to also do a LOT of validations. My system (and therefore my appdata directory) is on a Samsung 960 EVO M.2 1TB SSD. You have to search far and wide to get anything faster than this drive. It tests out at about 10x a normal SSD. But my system was still locking up for several minutes at a time, even with 2019.1 while in browse. But since of this exclusion, I have not seen this problem0
Yeah, I left my cache folders alone.
I'll play around with PR2019 this evening to see if the virus program exclusion setting improves performance on my machine. Thanks for the tip, any help making the software run better is most welcomed!0
Okay guy's so i guess i'll leave the scratch disk alone for now appreciate the conversation on working the bugs out in the meantime I'm rolling back, uninstalling 2019.1 and re-installing the previous version at least that did not crash seems like other users are beginning to see crashes also.0
Well, first image I tried processing this evening PR2019 locked up and froze my whole machine up. I waited for 20 minutes and finally just had to do a forced restart on my machine to close it out....
This is beyond frustrating.....................................0
I just restarted everything and re-opened PR2019 and left it in browse only and the CPU is maxed out at 100% (it's been in the high 90's and at 100% for 10 minutes now) and I am not doing anything!!!
I'm not using cataloged folders......
I closed PR2019 and then opened PR2018.5 and that opened fine and is running great, I started browsing through folders and working browse good and the CPU seldom ever went to 50% and when I stopped and let the program just sit it just idled at around 10% on the CPU.
PR2019 is obviously the problem...............absolutely everything on my machine is working great except PR2019.1
Arrh Jim sorry to hear that. Agree 2019.1 is definitely the problem and it is frustrating. Are you on a Windows or Mac0
I'm using Windows 10 Charles, if I open and close PR2019 a few times watching the task manager sometimes it'll open up and instantly be a low CPU and Memory level and I can use it for a while....makes no sense.
Support can't seem to sort it out and I've tried about all I know to do. I'll just have to let it play out like I did with PR2018, eventually ON1 came out with an updated build that finally would work on my machine.
Like I said in an earlier post, I'll probably get PR2019 working right and usable right about the time PR2020 is about to be released and then I can download PR2020 and start the whole process over again! LOL1
My sentiments exactly Jim I've hardly used 2019 since I bought it back in November it just doesn't make any sense 0 problems with 2018 in 2019 is barely usable0
Thank-you very much Kevin for sharing this suggestion. I saw immediately a general improvement in the responsiveness of ON1 2019.1. Happy New Year.0
Your welcome Antoine. It has been a frustrating ride using 2019. The release of 2019.1 was better. But better is a relative word. Better than 2019 yes, but not even close to better performance than 2018. I have to say that I have never seen a piece of professional software released (2019) with as horrible performance as compared to the previous major release. And that is saying something as I have been deeply involved in the computer software field for over 40 years. I just hope they learned something of the experience and do a better job of testing and debugging before releasing from now one. It might pay for them to send someone to be trained by a larger company in the better ways of doing this.2
Can you describe in a little more detail what you meant when you said, "I made some additional adjustments to the exclusion list that my antivirus and anti-malware use." How did you do that? Where do you go to do that? Does this have anything to do with a Whitelist?0
Before doing any "adjustments" just turn off your virus and anti-malware protection. With the virus protection turned off, see if things work any better in ON1. It should be noticeable, so if you are not sure, or not really able to tell if it is helping with the virus protection turned off, then this solution is not going to help you. So turn everything back on.However, if you do see an improvement in performance, try and add the exceptions in the anti-virus and anti-malware configuration.
Whatever you decide, make sure you turn the anti-virus and anti-malware software back on.
I use AVG virus protection and when it sees a program making changes to my system drive, AVG will prompt me and ask me if I want to allow it. If I say yes, it does add the program to a whitelist.
But what I am describing is a bit different than a whitelist. I am telling AVG to not monitor certain directories on my system drive and also my system. So it keeps it's nose out of those areas. I can specify directories to exclude from monitoring.Each anti-virus and anti-malware does things a little different, but they all should have a way of doing this.
In AVG, this is done in the General configuration section under Exceptions. The description in AVG says this: "Type Paths and URLs to be excluded from scanning and from all shield protection. Be careful when modifying these exceptions as any mistake might put your PC at risk."0
To follow Kevin's guidance, but using Win10 built in Virus detection.... You can get to the "Exceptions" settings by the following steps:
Windows Search > Windows Defender Settings > Virus & Threat Protection > Virus & Threat Protection Settings > Manage Settings > Exclusions > Add or Remove Exclusions
In my case, I felt comfortable adding the directory exception as noted by Kevin. I also added the file type "on1".0
So, here is an interesting wrinkle...
I'm working on a series of raw files, and my process is to choose my first file in Browse, then go into Edit, change to Filmstrip view, do some cropping, hit the "Apply" button to keep the crop, hit the "Auto" button in the Tone section, make some minor adjustments in the Color section, and then choose the next file in the filmstrip, and repeat these steps.
While doing this, almost every step in the process freezes the mouse for 3-5 seconds, and CPU usage ranges from 30% to 90%. Just about unusable, even though I've made all the performance changes suggested in this thread.
Then I noticed that, after choosing my first file and going into Edit, the problem does not exist until I get to the second file from the filmstrip and start going through the above steps.
So... For my next batch of files, instead of using the Filmstrip view in Edit so I can go from file to file, I just used the view without the filmstrip at the bottom, and when I'm going to my 2nd file, 3rd file, etc., I go back into Browse to choose it and then come back into Edit. And wouldn't you know, I'm not getting any of the performance problems when I do it this way!
So, going back and forth between Browse and Edit for each new file I'm working on has no performance problems, but staying in Edit and using the Filmstrip view to go from one file to the next is so slow it's almost unusable!
Anyone else notice this?
Export is still very slow & has high CPU usage, and every once in a while, On1 just closes on me, but leaves a background process running in Task Manager. Then I cannot open On1 again, even after closing the background process - I have to reboot my PC.
Using the steps you describe, I see a pause, but it is less than 3s (probably less than 2). It looks like a progress bar opens when I move to the next image. It seems like On1 is finishing reading in the next RAW image.
I use another tool that does a pre-fetch one image before and one mage after the image that is being edited. The result is a bit greater memory footprint... but the change to the next image is instant.0
Please sign in to leave a comment.