TernFS – An exabyte scale, multi-region distributed filesystem
1–10 of 111 posts
Re: TernFS – An exabyte scale, multi-region distributed filesystem
#2> TernFS should not be used for tiny files — our median file size is 2MB.
Re: TernFS – An exabyte scale, multi-region distributed filesystem
#3Cool project and kudos for open sourcing it. Noteworthy limitation: > TernFS should not be used for tiny files — our median file size is 2MB.
Re: TernFS – An exabyte scale, multi-region distributed filesystem
#4Re: TernFS – An exabyte scale, multi-region distributed filesystem
#5Cool project and kudos for open sourcing it. Noteworthy limitation: > TernFS should not be used for tiny files — our median file size is 2MB.
Re: TernFS – An exabyte scale, multi-region distributed filesystem
#6Re: TernFS – An exabyte scale, multi-region distributed filesystem
#7How does TernFS compare to CephFS and why not CephFS, since it is also tested for the multiple Petabyte range?
Main factors:
* Ceph stores both metadata and file contents using the same object store (RADOS). TernFS uses a specialized database for metadata which takes advantage of various properties of our datasets (immutable files, few moves between directories, etc.).
* While Ceph is capable of storing PBs, we currently store ~600PBs on a single TernFS deployment. Last time we checked this would be an order of magnitude more than even very large Ceph deployments.
* More generally, we wanted a system that we knew we could easily adapt to our needs and more importantly quickly fix when something went wrong, and we estimated that building out something new rather than adapting Ceph (or some other open source solution) would be less costly overall.
Re: TernFS – An exabyte scale, multi-region distributed filesystem
#8Cool project and kudos for open sourcing it. Noteworthy limitation: > TernFS should not be used for tiny files — our median file size is 2MB.
What happens if you put a tiny file on it then? Bad perf, possible file corruption, ... ?