VOGONS

Common searches


Search results

Display options

Re: The downfall of Firefox

in Milliways
... Booted in XP 32, so I only have 3 GB usable RAM ... If I understand right you have the typical problem of 4GB of physical RAM installed, but a 32-bit Windows that ignores and wastes ~0.75GB of memory. That's the ideal scenario for nesting a ramdisk in 'The Forbidden Zone', to use the RAM that …

Re: The downfall of Firefox

in Milliways
The main drawback of using RAM disks is that information is lost after powering down. Any decent ramdisk can save an image to HDD before shutdown, and load it again after booting. I use batchs to load just the PaleMoon Profile to ramdisk after boot, and save it to HDD before shutdown (much faster). …

Re: The downfall of Firefox

in Milliways
Jorpho wrote: ... why not just configure the browser to stop writing to disk and/or to use more RAM directly? That can be done in Linux, but as far as I know not in Windows, unless via ramdisk.

Re: The downfall of Firefox

in Milliways
Isn't using a ramdisk for a browser by definition the same as disabling disk caching entirely? Nope nope, browser still caches, only instead of doing it on slow, crawling devices like an HDD ... http://www2.picturepush.com/photo/a/9818390/220/9818390.gif ... or an SSD ... http://www2.picturepush. …

Re: The downfall of Firefox

in Milliways
This is what I do to make PaleMoon go hypersonic (works equally for Firefox). - Move the whole PaleMoon/Firefox Profile folder to a ramdisk . - Move PaleMoon/Firefox disk cache to a ramdisk . - Tactical touches in about:config : network.http.pipelining.maxrequests ····· user set ····· integer …

Page 37 of 44