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

Reduce CPU, IO activity and UDP transmissions (peak+avg) #15

Closed
synctext opened this issue Mar 9, 2013 · 11 comments
Closed

Reduce CPU, IO activity and UDP transmissions (peak+avg) #15

synctext opened this issue Mar 9, 2013 · 11 comments

Comments

@synctext
Copy link
Member

synctext commented Mar 9, 2013

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)
Tribler-6 1-R31883-MAC-98percentCPU-309packetpersec-march2013

IO view:
Tribler-6 1-R31883-MAC-99percentCPU-360diskpersec-march2013

boudewijn-tribler pushed a commit to boudewijn-tribler/tribler that referenced this issue May 7, 2013
@ghost ghost assigned corpaul and whirm May 8, 2013
@NielsZeilemaker
Copy link

Can you confirm the cpu usage for the current devel branch?
Currently Tribler is behaving very nicely at my laptop, nicely skipping a lot of Bloomfilters (+/- 80%) resulting in a cpu load of 0-5%

@whirm
Copy link

whirm commented May 31, 2013

with debugging disabled?

@NielsZeilemaker
Copy link

I guess he's running a released version, hence it would have debugging disabled.

@whirm
Copy link

whirm commented May 31, 2013

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.

@NielsZeilemaker
Copy link

Just wait a bit, the skip will only work after receiving all data.

2013/5/31 Elric Milon [email protected]

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-18743804
.

@whirm
Copy link

whirm commented May 31, 2013

Its been running for around couple hours now. I will wait a couple more.

@whirm
Copy link

whirm commented May 31, 2013

Ok, I'm just under 80% now and CPU around 10% just for the python process. (debug enabled)

@synctext
Copy link
Member Author

synctext commented Jun 1, 2013

Always happy to test the latest branch, looking at Jenkins OSX build...
Got stuck: #166 .

@whirm
Copy link

whirm commented Jun 3, 2013

I got to ~85% skip at home. @synctext you can test again now that #166 is closed.

@synctext
Copy link
Member Author

synctext commented Jun 7, 2013

Congrats!

No more 110+% CPU usage!

You manage to create a Tribler which does not kick the fan into action.
CPU usage is significantly reduced. Guess there is further room for improvements on IO usage, but that is no longer a high priority.
streaming_cpu_usage

@dennyhalim
Copy link

idle (no download/upload) on my linuxliteos (ubuntu trusty based),
tribler cpu usage is always 40%-100%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants