Transmission

livings124 wrote:

slyborg wrote:Spoke too soon on b9945

I should of said the nightly build that should have fixed the cpu issue is at a minimum 9947.

Ok. Latest available on xpjets link above is 9945 (?) Via the "latest" link. I don't want to build the thing myself...

Spoke too soon on b9945 ;_; Looks like it's still doing it, I was confused because istat was reporting the process as 'launchd', before it was showing up as Transmission itself. Running top shows it as Transmission. What's odd is that it did seem ok for an hour or so. I see it spiking to 100% once ...

livings124 wrote:slyborg: this is with the latest nightly, as I just stated in the post above?

No, beta 5, as I indicated. Let me try the nightly....

Edit: Hm, looks like you found that nested loop Much better, no unusual CPU usage with same torrents on b9945. Thanks....

Related note...I may just not have noticed this before, but I see Transmission burst up to 100% CPU on one core for 30-40 secs every 4-5 minutes. This is with 3 torrents each single tracker and ~700 known peers total. I think this is new behavior, actually, because it's kind of annoying when running ...

So I gather that 1.76 and previous are doing this wrong? Or just displaying for the first tracker?

I would assume you could collect the entire peer list from all trackers and discard duplicates to obtain a correct count. I would agree this seems like a lot of work for this information. As an ...

Why was the Peers interface of the Inspector changed? This previously had pretty much all the relevant information for the torrent in one place, now the summary of Total Seeders, Total Leechers, and Total Downloaded is in the Tracker Inspector pane. Also the new 2-line centered format is harder to ...