Opened 13 years ago

Closed 13 years ago

#3316 closed Bug (invalid)

CPU usage in Transmission 2.0 increased

Reported by: Sato Ambush Owned by: Livings124
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.00
Severity: Normal Keywords:


I am running transmission 2.0 on a powerbook 1,67 Ghz with OSX 10.5.8 installed (all latest patches applied). Since the update to transmission 2.0 and the update to Itunes 9.2 my system was stalling from time to time, which made me suspicious. In Transmission itself i've switched on grouping as sorting method i've chosen "activity". In the terminal top shows in between ~20 to ~30% cpu usage for plain seeding. If i switch to the sortingmethod progress the usage is inbetween ~10 and ~20%. But in general the cpu usage was way lower in < 2.0.

Change History (6)

comment:1 Changed 13 years ago by charles

Hey Sato,

Thanks for the feedback. I've been trying pretty hard to get CPU use /down/ in 2.0 so I take reports like this pretty seriously... could you please attach a textfile shark report following the steps listed at ?

comment:2 Changed 13 years ago by Sato Ambush

i just ran shark when i returned home. cpu was again jumping in between 20 and 30 approximately. but the upper top wasn't reached that often this time. but hope that the shark profile helps a bit. if you need any more or any further more specific infos let me know. best regards

comment:3 Changed 13 years ago by livings124

  • Component changed from Mac Client to Transmission

comment:4 Changed 13 years ago by charles

Sato: could you make another shark report from a nightly build?

Also, I don't see any libtransmission calls in that shark report. Typically shark reports look more like ... are you sure you followed the wiki page's instructions?

comment:5 Changed 13 years ago by charles

Sato: ping

comment:6 Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. Thanks again!

Note: See TracTickets for help on using tickets.