Chrome/Safari cache is written to your SSD by default — slowing things down and shortening SSD life. Move the cache to a RAM disk for noticeably faster browsing and 2 more years out of your aging SSD.
🔧 Technical Details
RAM Disk Cache creates a RAM disk using macOS built-in hdiutil (128MB-256MB) and redirects Chrome/Safari browser cache paths to it. Chrome uses the --disk-cache-dir startup parameter, while Safari modifies WebKit cache preferences in its plist. A shell script with launchd plist ensures automatic mounting and symlink setup on every boot. All logs saved to ~/.mars-toolkit/logs/ram-disk-cache.log.
❓ FAQ
How much RAM does this use? Will it affect my daily workflow?
Default allocation is 128MB, max 256MB. On any Mac with 4GB+ RAM this is negligible. The RAM disk only consumes space when cache data is actually stored — it's mostly empty. If you have a 4GB machine, you can manually adjust it down to 64MB.
Does the cache disappear after reboot? Won't the browser need to re-cache everything?
Yes, it disappears — and that's a good thing. Browser cache is inherently temporary: images, CSS, JS files. After reboot they'll be re-cached on first load, then the speed boost resumes. The tiny cost of one re-cache is far outweighed by reducing daily SSD write wear.
Which browsers are supported?
Chrome and Safari are supported out of the box. Chrome uses the --disk-cache-dir flag; Safari uses WebKit preference changes. Firefox users can manually configure browser.cache.disk.parent_directory in about:config. Edge and other Chromium-based browsers work the same as Chrome.