From 0a274fe77f64456536119b5e6ad0697f69e6d9eb Mon Sep 17 00:00:00 2001 From: Jakob Unterwurzacher Date: Mon, 8 Dec 2014 19:37:30 +0100 Subject: [PATCH] Mention PERFORMANCE.md in README.md --- README.md | 35 +++++++++++++++++++++++------------ 1 file changed, 23 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 43690f2..a63501a 100644 --- a/README.md +++ b/README.md @@ -33,19 +33,30 @@ depends upon community interest. In order to make it easier for anyone to contribute, it is moving a new home on Github. So if you're interested in EncFS, please dive in! -EncFS still has a few unique features that may be interesing to you: +## Unique Features -* `--reverse` mode: Provides an encrypted view of an unencrypted folder. - This enables encrypted remote backups using standard tools like - rsync. -* EncFS is typically faster than ecryptfs for stat()-heavy workloads - when the backing device is a classical hard disk. - This is because ecryptfs has to to read each file header to determine - the file size - EncFS does not. This is one additional seek for each - stat. On SSDs that have virtually no seek time, that difference may - disappear. -* EncFS works on network file systems (NFS, CIFS...), while ecryptfs - is known to still have [problems][1]. +EncFS has a few features still not found anywhere else (as of Dec 2014) +that may be interesing to you: + +### Reverse mode + +`encfs --reverse` provides an encrypted view of an unencrypted folder. +This enables encrypted remote backups using standard tools like rsync. + +### Fast on classical HDDs + +EncFS is typically *much* faster than ecryptfs for stat()-heavy workloads +when the backing device is a classical hard disk. +This is because ecryptfs has to to read each file header to determine +the file size - EncFS does not. This is one additional seek for each +stat. +See [PERFORMANCE.md](PERFORMANCE.md) for detailed benchmarks on +HDD, SSD and ramdisk. + +### Works on top of network filesystems + +EncFS works on network file systems (NFS, CIFS...), while ecryptfs +is known to still have [problems][1]. ## GitHub Transition