Excessive CPU Usage

[exiva]

r9929 seems to be using an excess of CPU. Much much more than 1.76 uses. Almost a steady 70-100% I actually think this might be related to the fix for #2416

I'll do some testing and reply to this with what I find.

[exiva]

for comparison, r9837 uses about 30-35% CPU. (The earliest version I have on my computer.) The last build I have before the fix was implemented for #2416 uses about is r9899 and the same 30-35% cpu before it crashes. However, in r9929 it's a constant 70-100%

[livings124]

Could you do a shark trace (​http://trac.transmissionbt.com/wiki/Shark) and report back.

[exiva]

Shark Trace right after starting the application

[exiva]

Shark Trace after the app has been running for a few minutes

[exiva]

Replying to livings124:

Could you do a shark trace (​http://trac.transmissionbt.com/wiki/Shark) and report back.

Added two shark traces.

[charles]

Thanks exiva. I'm not positive, but it seems to me that those shark traces agree with you, that the #2416 workaround of having libevent use poll() rather than kqueue() uses more CPU. The libevent developers are working on a fix for their kqueue() code, but it's an open question whether it will be done in time for 1.80...

What version of OS X are you using?

[exiva]

Replying to charles:

Thanks exiva. I'm not positive, but it seems to me that those shark traces agree with you, that the #2416 workaround of having libevent use poll() rather than kqueue() uses more CPU. The libevent developers are working on a fix for their kqueue() code, but it's an open question whether it will be done in time for 1.80...

What version of OS X are you using?

I'm running 10.6.2 with all the latest updates.

[jortuny]

I can definitely confirm this bug, and my shark trace looks pretty similar. Happened right after the switch to poll(). With many torrents open transmission now pegs one core at 100% which is fairly annoying.

[livings124]

r9946 is using the kqueue backend again. exiva and jortuny, please update, test, and report back, whether it's good news or bad news.

[livings124]

r9947, that is

[jortuny]

I ended up removing a vast majority of the torrents I was on because of the CPU usage :-(. But I'll download and test anyways since even with only a few when seeding it pegs the CPU and see what happens.

[livings124]

In my own tests I have confirmed the switch back to kqueue has resolved this issue. Please reopen if this is not the case with a current nightly build.

[jortuny]

Yep, it seems fine now.