raft VS torrent

Depending on your exact needs, you could try HashiCorp's Raft implementation: https://github.com/hashicorp/raft

I have found the performance tests very tricky to get to pass without having any input from others. The assignment is really very unforgiving, I would wager the test suite is comparable to how commercial Raft implementations are tested (e.g. https://github.com/hashicorp/raft)

While searching on GitHub, I found a pull request in the Raft implementation by Hashicorp (a distributed consensus algorithm), which we can use to demonstrate the following problem. Let’s start by showing the code (at api.go):

Hey,

you could inspire yourself by hashicorps raft implementation written in go and build one for typescript. Code is quite good to read and Go ins't that far away from typescript.

https://github.com/hashicorp/raft

Production-grade distributed consensus system.

In general Hashicorp's repos are high quality:

https://github.com/hashicorp/raft

Example application: https://github.com/Jille/raft-grpc-example

https://github.com/anacrolix/torrent has a fuse driver since 2013. I'm in the early stages of removing it. There are WebDAV, 3rd party FUSE, and HTTP wrappers of the client all doing similar things: serving magnet links, infohashes, and torrent files like an immutable filesystem. BitTorrent v2 support is currently in master.

I'm the author of https://github.com/anacrolix/torrent (started in 2013) and https://github.com/anacrolix/dht (started in 2015). I have a DHT indexer implementation I developed in 2021. It's currently closed source but available for use as part of https://www.coveapp.info/. I have found that after several hours the search is excellent and stays up to date with ease.

https://github.com/anacrolix/torrent/blob/master/cmd/torrent... does exactly that. Install with `go get github.com/anacrolix/torrent/cmd/torrent@latest`, and then run `torrent serve `.

Hit me up if you want to discuss using BitTorrent to back images. https://github.com/anacrolix/torrent

It has some small latency but only when resources are spread across many different infos. If you can constrain your resources to a single DHT traversal, it's pretty quick. I run several services that stream from BitTorrent on demand, using https://github.com/anacrolix/torrent which are surprisingly quick to start. However it does choke up when you try to start many different resources at once, which multiplies horizontally the number of DHT traversals, and per-torrent related overhead to get started.

It is solvable, but any solution that spreads resources out across many different targets in the DHT is slow. Basically anything that was inspired by BitTorrent, but isn't BitTorrent itself does this, because they get overly excited by deduplication of data.

For whatever reason the ARM version Transmission does not work well on my M2 laptop - it downloads quickly at first and then drops off to zero. I tried playing around with different settings, running their nightly builds, etc, and nothing fixed it for me. In the end I searched for other clients and found them all filled with ads and bloatware, and decided to use this excellent open source command line client instead:

https://github.com/anacrolix/torrent

It has a few frontends built on top of it (linked in the project readme), but I just run `torrent download ` and it downloads at full speed / with no issues.

https://tcloud-lunik.herokuapp.com/ https://btorrent.xyz/ https://github.com/pldubouilh/webtorrent-webui https://github.com/anacrolix/torrent

The use case is in the refactoring in https://github.com/anacrolix/torrent/compare/smartban...lazylog. A lot of the parameters moved around as part of a performance optimization in https://github.com/anacrolix/log/compare/lazylog.