I got rida ZFS and am so happy.
I wish i could tell firefox to not hit disk. So browsing would be faster.
Caching generally improves browsing, not slow it down. What makes you think it would be faster?I wish i could tell firefox to not hit disk. So browsing would be faster.
Perhaps more interestingly, why are you so happy to be rid of ZFS?
Since I don't use Firefox, I can't say if this page is up to date. But according to it, you can set your profile directory with the -profile parameter.
Simply mount a tmpfs(5)-based filesystem (/tmp would be good), use a script to populate a directory there (e.g. /tmp/myffprofile) with previously-saved profile files and run Firefox using that parameter.
I run fire fox with these plugin:Honestly speaking, I don't understand what is slow in Firefox. Really! I use it exclusively many years, never noticed things mentioned by many people here on the Forums.
Would somebody bring an example please?
Caching generally improves browsing, not slow it down. What makes you think it would be faster?
Yes, but RAM is generally in short supply compared to disk space. And caching usually involves a mix of both RAM and disk usage.Ram is faster than disk.
Caching is really the only reason why Firefox would "hit the disk".You imply that I said caching slows down an app? I did not say that.
That depends on how exactly the caching mechanism is implemented. Most mechanisms read stuff into RAM and only write to disk (which can happen asynchronous) once it's been processed. The next request for the same data will then be read from disk to RAM instead of the network to RAM, and disk to RAM is typically faster.If data came from network into ram without hitting disk, that would be a lot faster, no?
This is probably more related to how pages or content is rendered. In these cases there will be very little caching, only some buffering, and this doesn't require a lot of CPU. Rendering the content however could use a lot of CPU cycles.But if I skip downloading and jsut play say 7 movies....firefox way way way slower, and iceWM little load graph goes to 100%....while in chrome it stays like 10% with tiny spikes....even with chrome playing 7 movies...
Yes, but RAM is generally in short supply compared to disk space. And caching usually involves a mix of both RAM and disk usage.
Caching is really the only reason why Firefox would "hit the disk".
That depends on how exactly the caching mechanism is implemented. Most mechanisms read stuff into RAM and only write to disk (which can happen asynchronous) once it's been processed. The next request for the same data will then be read from disk to RAM instead of the network to RAM, and disk to RAM is typically faster.
There's also the issue of reading so much data into RAM the system will start swapping. This is certainly not ideal. So you're left with a small amount of RAM that's actually available for caching, and means it's going to be flushed quite frequently (high cache-miss ratio), causing data to be constantly fetched from the internet.
This is probably more related to how pages or content is rendered. In these cases there will be very little caching, only some buffering, and this doesn't require a lot of CPU. Rendering the content however could use a lot of CPU cycles.
And now a lighthearted build comparison. firefox-56.0_1,1 took 00:24:58 to build, chromium-61.0.3163.100_1 took 16:04:59. ccache might not make this a completely fair comparison, but thundering gezzus that's quite a difference.A lighthearted security compassion...
It might, it might not.Is using /tmp a way? As one user suggested?
That depends on how you configured your system. With a standard install /tmp is just a filesystem on disk. A lot of people (myself included) use tmpfs(5) for /tmp.Is that a ram backed disk area or something?
Yes.Will it dynamically take needed memory?
No, but you can set a maximum:or do you set it to use N amount?
size Specifies the total file system size in bytes. If zero (the
default) or a value larger than SIZE_MAX - PAGE_SIZE is given,
the available amount of memory (including main memory and swap
space) will be used.
Don't forget the mode=1777 permissions or you will get some weird errors with certain applications.Ok I see example in fstab man page...ok cool.
Don't forget the mode=1777 permissions or you will get some weird errors with certain applications.
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ada0p2 447G 22G 389G 5% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/ada1p1 451G 299G 116G 72% /a
/dev/da0 4.4T 2.8T 1.3T 69% /vogt
tmpfs 16G 139M 16G 1% /tmp
$ cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
/dev/ada1p1 /a ufs rw 2 2
tmpfs /tmp tmpfs rw,mode=1777 0 0
https://lifehacker.com/5687850/speed-up-firefox-by-moving-your-cache-to-ram-no-ram-disk-required firefox wouldn't start when I moved .mozilla to /tmp after mounting tmpfs......
Your configuration used tmpfs. I had md(4) for /tmp through /etc/rc.conf. md can be found in rc.conf(5) as tmpmfs:Code:tmpfs /tmp tmpfs rw,mode=1777 0 0
tmpmfs="YES"
tmpsize="16g"
#tmpmfs_flags=""
ln -s
, to root /tmp. You could alternatively run tmpfs for every directory or temporary file.Use editors/leafpad or other desktop text viewer to open it, to copy and paste. I often use the terminal toI can't paste from xterm to chrome on this forum
>
or >>
output into a file to be opened. You can use ~/.Xdefaults to configure copying from a terminal, but you'll have to look through various documentation to do that.