Live data from Hacker News

SeaweedFS fast distributed storage system for blobs, objects, files and datalake

github.com

1–10 of 128 posts

Re: SeaweedFS fast distributed storage system for blobs, objects, files and datalake

#3
post #2

I was asking around in my network after experience with self hosting S3 like solutions. One serious user of SeaweedFS recommended looking into min.io instead. Another serious user of min.io recommend looking into SeaweedFS instead…

Sounds like you should try both and write an article!

Re: SeaweedFS fast distributed storage system for blobs, objects, files and datalake

#5
post #2

I was asking around in my network after experience with self hosting S3 like solutions. One serious user of SeaweedFS recommended looking into min.io instead. Another serious user of min.io recommend looking into SeaweedFS instead…

If your looking for more recommendations, try Garage ( https://garagehq.deuxfleurs.fr/ ), which is on my short list to try in my home lab...

Re: SeaweedFS fast distributed storage system for blobs, objects, files and datalake

#6
post #4

We tested both SeaweedFS and Min.io for cheaply (HDD) storing > 100TB of audio data. Seaweed had much better performance for our use case.

Any hiccups?

Drop in S3 compatibility with much better performance would be insane

Re: SeaweedFS fast distributed storage system for blobs, objects, files and datalake

#8
post #6
post #4

We tested both SeaweedFS and Min.io for cheaply (HDD) storing > 100TB of audio data. Seaweed had much better performance for our use case.

Any hiccups? Drop in S3 compatibility with much better performance would be insane

Setup is a little obscure, but the developer is responsive on Slack and GH.

We are only a couple months in and haven’t had to add to our cluster yet, storing about 250TB, so it’s still early for us. Promising so far and hardware has already paid for itself.

Re: SeaweedFS fast distributed storage system for blobs, objects, files and datalake

#10
post #4

We tested both SeaweedFS and Min.io for cheaply (HDD) storing > 100TB of audio data. Seaweed had much better performance for our use case.

Do you wish it supported Erasure Coding for lower disk usage, or is your workload such that the extra spindles from replication are useful?
Post reply on HN