From b0d785f0fa140a92a9c1c5398da5e9c55dd2a3a2 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Thu, 12 Nov 2020 15:58:24 -0800 Subject: [PATCH] Created Words from SeaweedFS Users (markdown) --- Words-from-SeaweedFS-Users.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 Words-from-SeaweedFS-Users.md diff --git a/Words-from-SeaweedFS-Users.md b/Words-from-SeaweedFS-Users.md new file mode 100644 index 0000000..24777d7 --- /dev/null +++ b/Words-from-SeaweedFS-Users.md @@ -0,0 +1,4 @@ +| Use cases | Details | Comments | +| ---- | -- | -- | +| replaced ceph with a seaweedfs under the docker registry in production | Under the registry half a million files. Not big but have intensive exchange. | Killer feature of seaweedfs is that it disign like S3 in yandex and can work in k8s and spread between data centers. Ceph has a bad design in the case of using a huge number of small files over 10 million, cluster recovery takes several days. The next step is to use instead of Glusterfs, which is now barely alive and is bent from 10 million files. | +| we use seaweedfs embedded in our AI products that are deployed on client site (usually AirGapped because of the sensitivity of the data)| clusters ranging from 3-10 servers (and now startiting to get bigger and bigger), usually retaining 7-14 days video and 30-60 days of thumbnails | we comared CEPH & Minio, we checked deployment procedure & maintenance and especially performance of writes and especially single server performance and easy scale out. we went and found that seaweedfs always won. we mainly write intensive and rarely read (usually reading as soon as write, so no real disk access) and 95% of the data is not missing critical, so the easiness of seaweedfs and the amazing performance (all writes are sequential as possible) | \ No newline at end of file