-
Notifications
You must be signed in to change notification settings - Fork 452
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
Reduce CPU, IO activity and UDP transmissions (peak+avg) #15
Comments
Can you confirm the cpu usage for the current devel branch? |
with debugging disabled? |
I guess he's running a released version, hence it would have debugging disabled. |
I was asking you, I'm running devel's HEAD with debug enabled and I get much more than that, around 30% most of the time. Also, around 25.9% skip and 58.4% reuse. |
Just wait a bit, the skip will only work after receiving all data. 2013/5/31 Elric Milon [email protected]
|
Its been running for around couple hours now. I will wait a couple more. |
Ok, I'm just under 80% now and CPU around 10% just for the python process. (debug enabled) |
Always happy to test the latest branch, looking at Jenkins OSX build... |
idle (no download/upload) on my linuxliteos (ubuntu trusty based), |
Tribler uses 30% average CPU usage in idle of v6.1 on a single i7 core.
Dependancy: insight in performance #6 and fix inefficiency # 1 (this ticket is repurposed).
Old Mac Book Pro performance (idle, no downloads, no seeding):
55% average CPU usage on older 2.2GHz Intel core 2 duo (with 99% peaks)
360 IO operations/second at peak
309 network packets transmissions/second at peak
Most expensive GUI operation:
Viewing a subscribed channel with thousands of torrents.
It takes 15seconds to respond and CPU goes to 130-140% range
System monitor networking view and Tribler Debug info (walker,drops,tracker,etc)
IO view:
The text was updated successfully, but these errors were encountered: