Cache Relocator does not redirect certain folders
2 posts
Hello.
These folders are not redirected to RAMdisk by the Cache Relocator program:
"C:\Users\username\AppData\Local\Google\Chrome\User Data\profilename\Service Worker\CacheStorage" "C:\Users\username\AppData\Roaming\Mozilla\Firefox\Profiles\profilename\storage\default"
Their size increases significantly when browsing in Chrome and Firefox, especially with Telegram Web. This means they can reduce the lifespan of the SSD.
I kindly request that you add an option in Cache Relocator to redirect these folders to RAMdisk, or that these folders be automatically redirected when a browser or profile is redirected to RAMdisk.
Thank you for taking the time to report this. We've now updated Cache Relocator to handle it.
In the latest snapshot build, Cache Relocator relocates all disposable caches: "Cache", "Code Cache", "GPUCache". Each browser and profile gets its own isolated folder on the target drive, and since a RAM disk is emptied on every reboot, the program now also installs a small logon task that recreates those folders automatically at start-up, so the redirection keeps working after a restart.
The "storage\default" folder of Firefox and the "Service Worker\CacheStorage" folder of Chrome cannot be redirected the same way because they hold some data that should be persistent, such as login sessions, site databases, and for web apps like Telegram Web and WhatsApp Web the actual message store and the credentials that keep you signed in. The good news is that genuinely disposable cache of Firefox (the HTTP cache - cache2, startupCache and similar) lives in a different place (%LocalAppData%\Mozilla\Firefox\Profiles) and Cache Relocator already redirects that. So the real cache is being moved off your SSD; it's only storage\default that has to stay in place, because it can't be treated as throwaway data.