You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

31 lines
1.1 KiB

  1. # Reliability and Scalability
  2. ## Is mergerfs "production ready?"
  3. Yes.
  4. mergerfs has been around for over a decade and used by many users on
  5. their systems. Typically running 24/7 with constant load.
  6. At least a few companies are believed to use mergerfs in production
  7. environments. A number of [NAS focused operating
  8. systems](../related_projects.md) includes mergerfs as a solution for
  9. pooling filesystems.
  10. Most serious issues (crashes or data corruption) have been due to
  11. [kernel bugs](../known_issues_bugs.md#fuse-and-linux-kernel). All of
  12. which are fixed in stable releases.
  13. ## How well does mergerfs scale?
  14. Users have reported running mergerfs on everything from OpenWRT
  15. routers and Raspberry Pi SBCs to multi-socket Xeon enterprise servers.
  16. Users have pooled everything from USB thumb drives to enterprise NVME
  17. SSDs to remote filesystems and rclone mounts.
  18. The cost of many calls can be `O(n)` meaning adding more branches to
  19. the pool will increase the cost of certain functions but there are a
  20. number of caches and strategies in place to limit overhead where
  21. possible.