Transmission

Thank you for responding... I thought I was going nuts so it is most good of you to confirm my suspicions.

I tried disabling DHT (distributed hash table) first in Transmission->Preferences->Peers section but there was no difference - cpu% for Transmission continued to be oscillate between 17-42 ...

Interestingly, I deleted *all* my torrents - thinking that perhaps the sheer number (even if they were all but one or two paused) was irritating Transmission. I started off with three completely new ones and thought the %CPU for Transmission hovered around 10-15%. I added 6 more after the first ...

Must be a more general thing since it seems that even if I just start up the most recent version of Transmission with everything (48 torrents, some local some on connected external drives) paused and nothing verifying it seems to sit around that 23% CPU mark. If I startup most/all of the torrents ...

I thought of that but none of the current torrents are listed as verifying. In fact only 2 of the list were active went it went to sleep and when it woke up.

I verified this behaviour by going to a third location and the problem reoccurred.

j

Window Shade X and Unsanity eradicated but the problem persists. From a fresh reboot, start Transmission. Put the MBP to sleep, bring to another location (aka completely different subnet and network path to inet), wake it up and, immediately before other things (like iChat and Skype, for example ...

I presume you mean Unsanity or one of the haxies that depend on it? Like WindowShade X?

That is the only application enhancer that I am aware of. Consider it removed if you suspect that is the issue.

j

I am not sure if I have been able to come up with the exact scenario to duplicate this problem but it seems that I see a 20-25% CPU utilization even when Transmission is paused and not downloading or uploading.

The problem seems to occur if I change network subnets such as going from one location ...