Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upbad cpu performance, not a viable bittorrent server solution #1381
Comments
This comment has been minimized.
This comment has been minimized.
|
Try webtorrent cli if you don't need to seed to webRTC peers (browsers) I don't think this project is really intended to compete with other bittorrent clients. Its purpose is to easily allow torrenting in browsers. I'm guessing that the CPU spike is caused by verifying the hashes of the torrents you're seeding, which is planned to be fixed. This extra CPU usage should dissapear once this is done though. You could spawn a seperate process for webtorrent and increase its nice value. That way it won't interfere with other processes regardless of its CPU usage. |
This comment has been minimized.
This comment has been minimized.
|
Known issue. I'm going to work on reducing CPU utilization soon. |
This is not a bittorrent replacement solution for servers running node , please make benchmarks to compare performance with other clients, running over 3 killed my CPU!! even with only one active torrent it still jumps to over 60% compared to transmission-daemon which ran smooth at 7-8% cpu.