Bug? Can't Change Brower Cache Location.
In Preferences, I keep both the Scratch Folder and Browser Cache in a separate SSD from my OS SSD. Not sure which of the recent updates changed the Browser Cache to my OS drive (the Scratch Folder is still where I want it) but now 2018.3.x will not allow me to change it back to where I want it.
The error I get is:
“The selected location must have enough free space to move the cache.”
On the wrong drive, the cache uses only 3.06 GB of space. There is over is over 84 GB of space available on the drive it should be on, so space is not the problem.
Any ideas? Anybody have this issue?
I have two SSDs as well, I just tried moving both the Scratch folder and browse folder from my OS SSD to my photos SSD and the move went off without a hitch. I just have to ask just because the error message is covering the preferences dialog -- are you sure the browse size value in the preferences dialog is not a huge number?0
Hi David. The cache size is not maxed out and is set to 8009MB. I'm guessing that's the default as I don't remember changing that value in prior releases. With more than 84GB of free space available on the target drive, there is plenty of room.0
Any body have any ideas? ON1's Priority Support was unable to help...0
I just added an SSD yesterday and moved both the cache and the scratch folder both to point to the root level of my SSD. ON1 created it's own folder for both of these. I have my cache maxed out at 10000. The folder on the root drive that ON1 created was called PerfectBrowseCache and it contains 46.1 GB of data. I know the cache size depends on if you have fast browse, accurate browse, and probably a few other things. So perhaps ON1 thinks about worse case scenarios and has a large number set aside. And then it looks at the amount of free space AFTER that calculation.0
Could it be a privilege issue? Can you use notepad to create a simple text file in the location you are trying to tell ON1 to use? If that works, then I would say it is not a privilege issue.0
Go into the Tools tab in the SSD properties dialog that you have shown. Try the Optimize button and if the dialog that pops up says that drive needs to be optimized, do it right then. Then try again. Also, you can also click the check button in the Tools tab. It will warn you if you need to actually check it and tell you about what it may cause while checking.0
I don't see anyone mentioning Emptying or reseting the cache and just making a new one. Is that not an option for some reason?0
The short version is with the clues above, it got it switched over. Thanks!
“Could it be a privilege issue?”
I’ve been using that drive for close to 3 years; it’s the same drive I take my screenshots in and do video capture on, so I’m good there.
“Go into the Tools tab in the SSD properties dialog that you have shown. Try the Optimize button and if the dialog that pops up says that drive needs to be optimized, do it right then.”
I don’t have an optimize button in my Properties popup anywhere, including under Tools. I’m running Win 7 Pro 64; maybe you have a different version?
While in the Tools tab, I did check for errors and the drive is good to go.
“I don't see anyone mentioning Emptying or resetting the cache and just making a new one. Is that not an option for some reason?”
Interesting, and I gave it a try. Resetting did set the cache size to 5000 MB but Emptying it did absolutely nothing!?!
So, in PR I clicked on Properties for the existing, default location and found that the cache files were a mix of regular and Read Only attributes. I cleared the Read Only box and Applied. I then tried to Move again, and this time it worked!
It took a very long time, though, for a SSD to SSD transfer. The Progress window when to 99% almost immediately, then seemed to hang. It took 4 minutes to finish, and that’s after I started timing it, so it took about 5+ minutes total.
In checking Properties of the new location, it too has mixed Read Only as in the screenshot below:0
Yes, mine is also shows the read-only mixed as well. I am using Windows 10 and that explains the missing optimize under tools. On Windows 10, the optimize button did a trim on the SSD. Windows should do automatic trims periodically. Even Windows 7. But you can check and make sure Windows 7 is doing the trim in the background. Here is one link which explains how to verify that is happening...
Just imagine how long it would have taken if you didn't do the reset! ;)0
I'm trying to solve agonizingly slow performance on my workstation. Xeon 3.2GHz, 16GB RAM, 1TB SSHD, Win7 (soon to upgrade). The Photo RAW 2019 Cache moved to my USB3 32GB drive with no problem, though it took many hours.
The PerfectBrowseCache has been a different story. I've tried five times now and it's failed each time with a message gives no info except to say an error occurred. Each time, it takes from 10-20 hours to get to the point where it fails, even with the cache cleared and set to 0. Most of that time, memory and disk i/o is maxed, so the computer isn't usable.
I've updated the video driver and PhotoRAW per the steps I found on support pages. Windows is updated as well. The USB drive has only the empty Photo RAW cache and nothing else. Moving the cache was the next step I found, but it's not going well.
I want to like the software, but I've got the latest release and it performs like a dog, even with video card tuned (GPU load is low, memory use is high, CPU load is medium). I have had no problem loading Lightroom, Photoshop, browsers, and more simultaneously, yet to run PhotoRAW, I usually have to shut down everything else to reduce wait times. My time is too valuable to have all this waiting!
At any rate, does moving the caches take forever for anyone else?
Has anyone put the caches on USB flash drives?
Any tips to boost speed?
Any help would be most welcome!0
Moving the cache does take a long time, but if your drive is 32 gig maybe it's just running out of room. My cache size is twice what your drive is.(66gig for 40,000 photos)
Without more info, it's hard to make a suggestion. Is this your first install? Do you have older versions that you need to keep? Are building catalogues? etc
If it were me, I would use the uninstall script to completely remove everything On1 and start over. Without the huge cache on a fresh install, you can move it more easily.
EDIT: By the way, there is also the option of moving your Roaming folder in Windows instead, well, in Win 10. Not sure if Win 7 can do that.1
I had completely uninstalled Photo RAW as part of troubleshooting but kept the catalog. I have a fairly large catalog of images (75-100k images, exports, and duplicates) from Lightroom, but the options say the cache is sized by default 4096, which would easily fit on the flash drive.
I'm using a Xeon 3.2GHz, 16GB RAM system with two internal drives - SSHD (SSD-HD hybrid) as the system drive and a 4GB platter drive for the data drive. I've got a couple of external/NAS drives for backups. This system has no problems running Photoshop, Lightroom, multiple tabs in Firefox or Chrome, and other editors, yet PhotoRAW brings the system to a crawl by itself.0
Actually, if I remember correctly, 4GB was the maximum for the browse cache and it would not allow more even on the system drive, which has quite a bit of space.0
You're confusing 2 caches. The PerfectBrowsecache is a hard drive location and has no limit. The cache size slider is for RAM.
From the user guide page 197
ON1 Photo RAW 2020 stores thumbnails previews on disk so that the next time you browse a folder it loads much faster. This setting lets you adjust the memory cache size as well as empty the cache, move it to another location, or reset it if you are having issues with Browse.
TIP: If you have a small solid-state drive as your boot volume, you should move
your cache to another drive, since the Browse cache can take up a lot of space
when you are using cataloged folders
That's how I understand it until someone tells me different.1
Ah Ha! I missed that "minor detail". That explains why it wouldn't go to the 32GB flash drive! The controls are a bit misleading in the way they're grouped. I'll see how it goes on the 7.2k rpm drive and move it back to the SSHD. Thinking about it, I suspect that the SSD portion of the SSHD might be too small to hold the cache, forcing slow disk reads.
I'll see how the faster drive works and might consider using a small SSD on eSATA to speed things up.
Tom, you probably found this by now, but 2020 has new options to help with bigger catalogs. See page 26 in the user guide.
An SSHD manages what goes in the SSD cache and what goes in the HD portion of the drive. Users have no control over that. You'll get much better performance if your cache is on a true SSD.1
Thanks for the info. I finally was successful in transferring the browse cache to my 2nd 7200 RPM drive and it's MUCH, MUCH faster. The SSHD caching was indeed the problem.
Rick and Brian, thanks much for your help!0
Please sign in to leave a comment.