Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bad cpu performance, not a viable bittorrent server solution #1381

Closed
poofyiq opened this issue May 7, 2018 · 2 comments
Closed

bad cpu performance, not a viable bittorrent server solution #1381

poofyiq opened this issue May 7, 2018 · 2 comments

Comments

@poofyiq
Copy link

@poofyiq poofyiq commented May 7, 2018

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.

@KayleePop

This comment has been minimized.

Copy link
Contributor

@KayleePop KayleePop commented May 9, 2018

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.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented May 9, 2018

Known issue. I'm going to work on reducing CPU utilization soon.

@feross feross closed this May 9, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Aug 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.