3 ms·

SeaweedFS is great as well. https://github.com/seaweedfs/seaweedfs https://github.com/seaweedfs/seaweedfs

• evanjrowley 2y ago
  Looks awesome. Been looking for some flexible self-hosted WebDAV solutions and SeaweedFS would be an interesting choice.
  • genewitch 2y ago
    depending on what you need it for nextcloud has WebDAV (clients can interact with it, and windows can mount your home folder directly, i just tried it out a couple days ago.) I've never used webdav before so i'm unsure of what other use cases there are, but the nextcloud implementation (whatever it may be) was friction-free - everything just worked.
• n_ary 2y ago
  Tried this for my own homelab, either I misconfigured it or it consumes x2(linearly) memory(working) of the stored data. So, for example, if I put 1GB of data, seaweed would immediately consume 2GB of memory constantly! Edit: memory = RAM
  • crest 2y ago
    Are you claiming that SeaweedFS requires twice as much RAM as the sum of the sizes of the stored objects?
    • n_ary 2y ago
      Correct. I experimented by varying the data volume, it was linearly correlated by x2 of data volume.
      • ddorian43 2y ago
        Create a reproducible issue in their github. The developer is very responsive.
  • TechDebtDevin 2y ago
    That is odd. It likely has something to do with the index caching and how many replication volumes you configured. By default it indexes all file metadata in RAM (I think) but that wouldn't justify that type of memory usage. I've always used mostly default configurations in Docker Swarm, similar to this: https://github.com/cycneuramus/seaweedfs-docker-swarm/blob/master/docker-compose.yml https://github.com/cycneuramus/seaweedfs-docker-swarm/blob/m...