List of Interesting Experimental Flags for Google Chrome to Try Out

Is there a Flag/settings in Chrome that will move cache to RAM without using RAMdisk?
In Firefox I do it via about:config but unsure on Chrome

The flag you are requesting does not exist.
If I understand your request correctly, there is a Chromium Command Line Switches:

List of Chromium Command Line Switches « Peter Beverloo

Code:
--disk-cache-size

that you should set to zero.

Code:
=0

I've never tried it and have no idea if it works, try asking @ Bot.
 
  • Block scripts loaded via document.write
  • TLS 1.3 Early Data
  • Parallel downloading
  • Strict-Origin-Isolation
  • Origin-keyed Processes by default
  • Isolated sandboxed iframes
  • Enable Fingerprinting Protection Blocklist In Regular Browsing
  • Device Bound Session Credentials (Standard)
  • Storage Access API follows Same Origin Policy
  • Local Network Access Checks - Enabled (Blocking)
  • Local Network Access Checks for WebRTC
  • Local Network Access Checks for WebSockets
  • Local Network Access Checks for WebTransport
 
There is this interesting flag in Chrome:

Code:
Use custom disk cache backend for HTTP Cache

It would seem advantageous to enable it.
But I did a little test with Lighthouse and it seems to me (although it's quite difficult to measure the before/after) that on my PC it's better to leave it at the default setting.

This isn't my area of expertise, so if there are any forum users who know how to check this better with other tools, I'd be interested in repeating their measurements to see if it's better to enable the flag.
Thank you.;) (y)
 
  • Like
Reactions: Sorrento
  • Block scripts loaded via document.write
  • TLS 1.3 Early Data
  • Parallel downloading
  • Strict-Origin-Isolation
  • Origin-keyed Processes by default
  • Isolated sandboxed iframes
  • Enable RenderDocument
  • Device Bound Session Credentials (Standard)
  • Local Network Access Checks (enabled blocking)
  • Local Network Access Checks for WebRTC
  • Local Network Access Checks for WebSockets
  • Local Network Access Checks for WebTransport
  • Local Network Access Checks with Split Permissions
 
  • Block scripts loaded via document.write
  • TLS 1.3 Early Data
  • Parallel downloading
  • Strict-Origin-Isolation
  • Origin-keyed Processes by default
  • Isolated sandboxed iframes
  • Enable RenderDocument
  • Device Bound Session Credentials (Standard)
  • Local Network Access Checks (enabled blocking)
  • Local Network Access Checks for WebRTC
  • Local Network Access Checks for WebSockets
  • Local Network Access Checks for WebTransport
  • Local Network Access Checks with Split Permissions

I am undecided whether to change this flag with the last option ((obviously not considering disabled):

3.png


4.png