Slow 2019 performance on fast computer
I have set up the gpu as you advise to get better performance but I find the workflow still to be a lot slower than Lightroom that I'm trying to replace. Is there anything more I can do to speed it up?
I'm running AMD Threadripper 2950X, 64 GB ram, m.2 drives, 1080 GTX and 32" 4k monitor. Using Sony A7R III and Fujifilm GFX 50S cameras.
This is with the latest version of ON1 Photo RAW 2019 (13.0.0.6139).
-
As what you say Sander, the software is not optimized for Windows at all; the ON1 staff need to solve this soon or next year if they do the same with new version without solve the bugs or the optimization, i didn't upgrade or renew my subscription until is fixed and stable as Mac version
1 -
I am having exactly the same issues. I have only recently started using ON1 so I don't have any experience with V18. However, this SW is simply unusable for me. I have never had any issues with Photoshop . I decided to try ON1 and there are a few of the features I really like. I have done all the setups as indicated and can see my GPU is being used, sometimes up to 40-50%. My issue seems more in the area of CPU usage, all 8 CPU's often run at 100%, not much disk I/O and memory often sits around 60-70% . I have just purchased a SSD drive to use as a scratch drive and may upgrade memory from 16G to 24G. But I am not confident that will improve my situation. I am somewhat surprised because all the video's I have watched most of the functions are quite good.
1 -
Yes i love On1 but the video you saw are almost from Mac Version if you notice, in 2019 they didn't make video with Windows version…..hope they fix soon the optimization and the bugs and give a good and stable software for Windows users.
0 -
I have a high-end computer and I too have these issues. Read here and see if this will temporarily fix the 2019 performance issues for you.
1 -
Thank you but i also reinstall OS 8 days ago and set all the possible optimization, On1 2019 goes well until you add many multiple layers and when you do and try to go back to develop from effetcs it start to be slow, and also when you push export button, none of this it is optimized by On1 staff for now and they do maybe on the next update. For now i have made all is possible and wait using 2018.5, i have no more time to loose around optimization - now it is up to the staff to solve and optimize on1 for Windows 10 and i wait…..
1 -
Kevin, did as you recommended and renamed the folder. On starting ON1, catalog is empty. Opened a folder via drive folders. Scrolling up and down was quick. Then did a PANO - 3 photo's (A7R2 so 42 meg) . Very CPU intensive and definitely slower than Photoshop but workable. Did a few quick edits which were all good. This time I too the advice I had read and went back to browse and did my export from there. So much better. Watched my CPU usage and it was not excessive.
Bit early to be conclusive as I would probably like to add a few more filters etc but first impression this is much better. I may get some time later tonight( Australia) but more likely tomorrow night to check it out properly. But if I can work like I did today I will be very happy. Great tip.
0 -
Anthony, glad it worked for you. I have been using ON1 since version 2017 and I really like the way the workflow is. It has always been a bit more computer resource intensive than I expected, but certainly usable for me. However this most recent problem with 2019, causing my computer to completely stop for as long as 6 or 7 minutes was a show stopper for me. Without the catalog, I am back working with 2019 again. I did submit a bug report and pointed them to my post with all of it's comments. Hopefully they will say that they are already aware of it and fixing it.
0 -
Ok, so I did get some time tonight to do some more editing. Few things I noticed. When I start with ON1, uses about 4-5G RAM. As I spend more time it climbs to around 8-9G . Even with Photoshop active did not get over 13G. This is very different behaviour to what I saw earlier. Running through my files in browse mode is very quick, no issues at all. Editing works fine . Noticeable improvement with the fix tool. Still a bit laggy but not bad - usable. The retouch brush takes about 2 sec for a small circle which is slower than photoshop but I can live with that. CPU usage is massively lower. Get the odd peak during an edit but system much more stable. Export is the only time I see my system go to 100% for all cores for 15-20 sec. All I am doing is exporting to a TIFF file. Conclusion, definitely much better than before but room for improvement.
1 -
I guess you figured out the mask question....:) One quick way is by right clicking inside of the small mask shown in the filter itself.
1 -
not a good application for heavy output photographer
1. no 1:1 preview rendering, i don't mind take times for 1:1 preview but when i start working just like cropping photos it still spent me 2 seconds for each photos
2. i had to output around 300 jpeg photos per each clients in 30 inches long edge with 300dpi, it took 2 mins for outputing 1 photo, just wasting my time actually.
iMac late 2017 40G Ram
1 -
Martin
I do a lot of event photography and will continue to use my current workflow. Where ON1 is very interesting to me are landscapes and birding where you dont have the high volume of photos.
0 -
I too have serious performance issues to the point where ON1 is completely unusable for me in a Windows 10. After even a modest amount of editing it usually crashes and completely disappears.
My system is spec'd adequately enough run Lightroom, Photoshop and video editing software without difficulty.
1 -
Support inspected a log file for me and found my graphics driver was old (which I thought was updated with the most recent!).
PR2019 has been unusable for me but when I did this update I can now use PR2019.....
I'm using a stock/standard HP Pavilion (approx. 3 yrs old) Laptop running Windows 10. The most recent Intel Graphics Driver is dated Nov. 5, 2018, so those running a machine similar to mine and or with Intel stock/standard drivers need to install the latest graphics drivers for your machine and perhaps it will resolve the issues you are having, it worked for me. PR2019 is still a bit buggy but at least I can use it now.
Be sure to check your machines spec's before doing this update.....
Intel has a newer driver which you can download here:
https://downloadcenter.intel.com/product/88355/Intel-HD-Graphics-520Thanks ON1 Support!!!!!
1 -
I am happy Jim you solved, Yesterday i made another try with a picture imported from On1 photo raw 2018 (using layers) in 2019 and i have made several Develop without great slowness, on the contrary i made any develop fast and it was better than i expected.
Only generating preview is stil slow and i notice when you call an export from effects it doesn't show the export background but only export now function; but if you came back in browse and do an export it is fast and and you can select export background instead of export now.
Updated driver and Windows 10 optimized (i reinstall the OS ten days ago) surely made an installation of On1 2019 fast and better if you have good PC specs, but some things are need to be optimized with the next patch to say at all: On1 2019 is a fast software to develop pictures.
0 -
Yes Alessandro, I've noticed exporting any where other than browse it generates a preview that takes a while. I keep forgetting to go back to browse to export and then have to wait! Just another trick to teach myself I suppose.
I haven't tried layers yet in 2019 so I'm still not sure 2019 is working correctly there yet. I shall play this evening with it and test some more. I'm looking forward to the patch or update that's soon to be released that'll fix some of these issues.
I'm keeping 2018 installed just in case 2019 acts up again! ;)
0 -
Today i made another edit of a raw portrait of a singer, all well when i use develop and effects and even portraits module….but when i add local adjustments the cursor or the brush goes choppy and slow as the past days before the OS reinstalling. No doubt the local adjustments have issue at all and if i need to use i go to On1 2018 for fast editing.
Next time i use On1 2019 i send another ticket to support and notice that.
0 -
Sharing the same experience. The browser on my iMac (3.2GHz, 24GB Memory) is painfully slow. Takes more than 5 minutes to load 100+ photos from a folder. Fetching from a QNAP NAS. Loading the same to Lightroom takes only moments. Thinking that On1 might only be useful for one-off editing. Sad.
0 -
Sorry for my plain English. It's not my mother language.
I had the same performance issues with Raw Photo 2019.5. Comparable to those described here. For example exports to jpg's took up to 2 minutes!!!
I tested a lot of workarounds. And it seemed as when ON1 performance went down the longer I worked with it.
What finally solved: I went to my laptop's system -> storage optimization and cleaned it. (about 4 GB smaller storage usage than before). After rebooting ON1 runs much faster, e.g. exporting now takes about 15 sec instead 1 to 2 minutes. Also most other functions run quite (not perfectly) smooth.
Seems to me, that ON1 doesn't communicate with Win10 storage / cache system as it should.
0 -
Running considerably better today - acceptable performance. Don't know what might have changed, but did the upgrade to 13.6.0. Nothing running on the NAS and the iMac is running pretty loaded (about 47% memory remaining). Makes me more comfortable in launching it for a post session.
Thanks for following up.
0 -
I just got a new 2018 Mac Mini with the fastest processor and upgraded to 32GB of RAM. I bought ON1 hoping it could be a replacement for Lightroom which had been running fine on my 2012 iMac until I just upgraded. ON1 on a new machine runs at 200% cpu when it's not even being used! This is quite ridiculous - how is there 200% cpu when nothing is being done? I was hoping to not have to subscribe to Adobe but it doesn't look like there is an alternative.
0 -
Did you set up any Catalogs? The cataloging process is resource intensive and pushes the CPU, GPU, & RAM usage quite a bit while the program renders all the images in the catalog(s). Once that process has finished all that overhead goes away.
I have ON1 running in the background right now and it is only utilizing 3.1% of the CPU.
I highly recommend that you add a small external SSD dedicated to ON1's Scratch space and Browse Preview Cache. Moving the preview cache there releases all that drive space back to the boot drive (you'll have to delete the original cache) and having a dedicated scratch drive removes I/O contention while editing which improves the program's performance. You don't want just one drive having to deal with the I/O for the OS, program use as it swap parts in & out of memory, parts of the image being swapped in & out, and the scratch space usage all taking place simultaneously.
0 -
Thanks for your input.
I imported all my stuff from Lightroom automatically. All the lightroom folders are showing up as catalogs. So based on what you are saying, rendering of the previews for every image in the catalog is happening in the background. The CPU continues to be pegged really high ( between 200-400% ) when I have ON1 running. I'll leave it running and wait for it stop the processing. I'm still not sure why it needs to be so CPU intensive. If someone clicks on a folder that would need to be rendered immediately but for a large catalog, it's very unlikely that someone is going be clicking through all the images. So this doesn't seem like a an architecture that would fit most usage patterns and it shouldn't be designed to be so CPU intensive.
I have my images on an external non SSD drive ( USB 2.0 and I should switch to usb-c ). I like your suggestion of a high speed preview cache externally but at this point, my main HD is an SSD so it's probably best to leave it there until I can invest in an SSD.
What is the requirement for the preview cache size? Number of images * some number proportional to thumbnail size?
Also I also thought ON1's database was supposed to be distinct from the folder structure but I'm seeing ".ON1" files in every folder in the catalog. Why is ON1 writing into the photo folder hierarchy?
EDIT: The CPU is currently showing 624% for ON1 - it varies continuously. Crazy
0 -
Yes, Importing your Lightroom library is very CPU & GPU intensive and it can take quite a while as the AI evaluates the image and creates the corresponding Photo RAW edits. It can take a couple of days for large libraries. While you may not click through all your folders, how is the program to decide which you will and which you won't?
I don't know the preview cache size requirements but I'd guess your equation is about right. I'm not an employee, just another user like you. :)
By default Photo RAW stores edits & metadata both internally and in those .on1 sidecar files. If you should ever have to completely uninstall the program you'll have backups of all that for when the program get reinstalled, you won't loose any edits. They also allow you to work on an image on multiple systems. Just copy the raw file, .on1, & .xmf sidecars to the new system and you pick up right where you left off.
They can be turned off in Preferences > Files > Sidecar Options.
0 -
Thanks for your feedback - it was very helpful for me to understand. I'll wait for the processing to finish.
A debate about the program design would be a never ending debate, and that's not my intention to start one, because it's obviously complicated and I can't and wouldn't claim to understand how ON1 works, but I certainly think it's possible to design the scenario to not be as CPU intensive as it is and I don't think the usage patterns matter. It might take slightly longer to generate the cache, but it would be a better user experience. Obviously there are outlier cases that make this difficult - such as if all the files are in one huge folder that's being catalogued as an extreme case and variations thereof, but then the user would run into that problem immediately. All users shouldn't be paying for an edge condition. Also this is one of the newer CPUs on the market so clearly the program isn't scaling - I wonder what would happen if I had an older computer. I remember reading a lot of users complaining about processing issues earlier.
For example:
And to add, I'm a little concerned about the computer. It's getting hot and I don't think any other program causes it to heat up like that. Also, I never hear the fan normally, but it's going really loud when ON1 is processing.
0 -
With your processor running at 200% continuously for so long I'm not surprised it is getting a little warm, mine did to. That too will stop once the cataloging has finished.
If you're concerned it's getting too hot, you can quit the program and let things cool back down for a while. The cataloging process will pick back up when you launch the program again. Another option would be to have a small desk fan blowing across the mini while this is finishing.
0 -
So checking in this morning running overnight the CPU is showing 600% this late morning. That's crazy.
0 -
This must be the new math I've heard about. In my day 100 out of 100 (100%) was the max. With this new math, I'm thinking that if I hack the CPU usage meter to read 1000% on my PC that I would never have a problem with any software again.
I have 4 cores in my CPU, but each one is 25% of the total, not 100%. I guess standards don't matter anymore.
By the way, On1 has maxed out my CPU (100%) plenty of times while catalogues are running.
0 -
Yes, but ON1 is the only software on my brand new computer pushing it that high. There is a problem with the design of the software in terms of performance. Now the CPU is sometimes low then alternatively spikes to a high number when I'm not using it. I hope the team figures this out. I have garage band running at the same time and even if I start a recording, Garageband is at 10% so the computer itself is not thrashing. I will still let it run hoping its the same issue Brian pointed out.
0 -
Each core may be 25% of the processor but each core has its own utilization rate. If each core is running at 100% then you wind up with the 400% processor. Yes, it is bad math but it makes it much easier for non-math users to understand how much of their system is being utilized.
0 -
This is a Mac, correct? I just wanted to add that on a Windows machine, there is a nice set of free tools that will monitor CPU usage, in particular core temperatures. I installed this software when I had earlier issues with ON1 PR. It is one thing for the processor to be used full tilt, it is another to run the processor into the high temp zone.
https://www.alcpu.com/CoreTemp/
0
Please sign in to leave a comment.
Comments
76 comments