Performance concerns about bittorrent-tracker HOT 7 CLOSED

Hey @coldwinds! There is currently no benchmark, but it's something that we should definitely test. Once a benchmark is written we can use it to optimize this module so it's competitive (and one day, better!) than opentracker! I think the simplicity of being to setup a tracker with a simple npm install is super compelling and hope to get this module there.

Do you have any experience with bittorrent trackers and/or writing benchmarks?

from bittorrent-tracker.

I recently made some changes for code simplicity that should also have an effect on tracker server performance. See this issue: #29

Let me know if you're interested in writing up some benchmarks or helping to test the performance.

from bittorrent-tracker.

Hi @feross, I'm not experienced with torrent tracker benchmark, but I think perhaps some web load / stress testing tools will do the job,

I collected some informations on tracker testing and it's hardware requirement

opentracker once setup a real world tracker to test it's tracker software

also because we could test the software with a huge amount of hashes and peers!

Source: http://opentracker.blog.h3q.com/

Demonii currently runs on a KVM based VPS on my own nodes. The main node is a Xeon X5677, and the VPS specs are 512MB RAM and 1000Mhz is still enough to run it now. When it needs more I can simply allocate more resources to the VPS.

Source: https://torrentfreak.com/pirate-bay-blessing-propels-new-bittorrent-tracker-to-great-heights-130525/

from bittorrent-tracker.

Opentracker is hand-optimized C. No way an implementation in any dynamically typed language is going to achieve that grade of throughput.

This module just received a refactoring which allows the data backend to be customized. I suggest you look for distributed high-perf databases to scale horizontally across many nodes.

from bittorrent-tracker.

Astro, are you planning to open source the new backend that you write for
bittorrent-tracker? That would be great to contribute back to the community
and I've love to run it at tracker.webtorrent.io.

On Mon Dec 15 2014 at 2:52:22 PM Astro [email protected] wrote:

Opentracker is hand-optimized C. No way an implementation in any
dynamically typed language is going to achieve that grade of throughput.

This module just received a refactoring which allows the data backend to
be customized. I suggest you look for distributed high-perf databases to
scale horizontally across many nodes.

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

from bittorrent-tracker.

PR #48 was especially important to us as this is going to be embedded in an existing application. The answer is no, unfortunately.

What are possible solutions to this Github issue?

from bittorrent-tracker.

I've heard somewhere (anecdotally) that a user was able to get near 1 million concurrent users using the UDP tracker (disabling HTTP and WebSocket). That's way better than I expected, though nowhere near what something like OpenTracker can get.

I'm personally not interested in trying to make this package compete with hand-optimized C (it's probably not possible). But PRs that improve performance are always welcome!

from bittorrent-tracker.