mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-11-20 06:56:27 -05:00
Misc doc updates
This commit is contained in:
parent
1b167d34d8
commit
095fcf82a3
5 changed files with 66 additions and 50 deletions
|
|
@ -1,34 +1,39 @@
|
|||
# Tweaking Performance
|
||||
|
||||
mergerfs is at its is a proxy and therefore its theoretical max
|
||||
performance is that of the underlying devices. However, given it is a
|
||||
`mergerfs` is effectively a filesystem proxy and therefore its
|
||||
theoretical max performance is that of the underlying devices
|
||||
(ignoring caching performed by the kernel.) However, given it is a
|
||||
FUSE based filesystem working from userspace there is an increase in
|
||||
overhead relative to kernel based solutions. That said the performance
|
||||
can match the theoretical max but it depends greatly on the system's
|
||||
configuration. Especially when adding network filesystems into the mix
|
||||
there are many variables which can impact performance. Device speeds
|
||||
and latency, network speeds and latency, concurrency and parallel
|
||||
limits of the hardware, read/write sizes, etc.
|
||||
configuration. There are many things which can impact
|
||||
performance. Device speeds and latency, network speeds and latency,
|
||||
concurrency and parallel limits of the hardware, read/write sizes,
|
||||
etc.
|
||||
|
||||
While some settings can impact performance they are all **functional**
|
||||
in nature. Meaning they change mergerfs' behavior in some way. As a
|
||||
result there is no such thing as a "performance mode".
|
||||
result there is really no such thing as a "performance mode".
|
||||
|
||||
If you're having performance issues please look over the suggestions
|
||||
below and the [benchmarking section.](benchmarking.md)
|
||||
If you're having performance concerns please read over the
|
||||
[benchmarking section](benchmarking.md) of these docs and then the
|
||||
details below.
|
||||
|
||||
NOTE: Be sure to [read about these features](config/options.md) before
|
||||
changing them to understand how functionality will change.
|
||||
NOTE: Be sure to [read about available features](config/options.md)
|
||||
before changing them to understand how functionality will change.
|
||||
|
||||
* test theoretical performance using `nullrw` or mounting a ram disk
|
||||
* test theoretical performance using `nullrw` or using a ram disk as a
|
||||
branch
|
||||
* enable [passthrough](config/passthrough.md) (likely to have the
|
||||
biggest impact)
|
||||
* change read or process [thread pools](config/threads.md)
|
||||
* change [func.readdir](config/func_readdir.md)
|
||||
* toggle [func.readdir](config/func_readdir.md)
|
||||
* increase [readahead](config/readahead.md): `readahead=1024`
|
||||
* disable `security_capability` and/or `xattr`
|
||||
* disable `security_capability` and/or [xattr](config/xattr.md)
|
||||
* increase cache timeouts [cache.attr](config/cache.md#cacheattr),
|
||||
[cache.entry](config/cache.md#cacheentry),
|
||||
[cache.negative_entry](config/cache.md#cachenegative_entry)
|
||||
* enable (or disable) page caching ([cache.files](config/cache.md#cachefiles))
|
||||
* toggle [page caching](config/cache.md#cachefiles)
|
||||
* enable `parallel-direct-writes`
|
||||
* enable [cache.writeback](config/cache.md#cachewriteback)
|
||||
* enable [cache.statfs](config/cache.md#cachestatfs)
|
||||
|
|
@ -41,7 +46,9 @@ changing them to understand how functionality will change.
|
|||
* use [tiered cache](usage_patterns.md) devices
|
||||
* use LVM and LVM cache to place a SSD in front of your HDDs
|
||||
|
||||
If you come across a setting that significantly impacts performance
|
||||
please [contact trapexit](support.md) so he may investigate further. Please test
|
||||
both against your normal setup, a singular branch, and with
|
||||
`nullrw=true`
|
||||
|
||||
## Additional Reading
|
||||
|
||||
* [Benchmarking](benchmarking.md)
|
||||
* [Options](config/options.md)
|
||||
* [Tips and Notes](tips_notes.md)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue