cpu maxes out after "errno 105 - No buffer space available"

[defaut.hostility]

hello. using version 1.52 here on my debian lenny box. dual xeon processors, 2gb memory, 100mbit connection.
I'm having a very frustrating time here.. i'm running daemon and after a couple minutes of seeding a torrent i lost access to web interface so i restarted transmission with -f flag so i could see what is going on..
it resumes the torrent and after only about a minutes time i get floods of these messages with different ips and ports:

Code: Select all

Couldn't connect socket 30 to xx.xx.xxx.xx, port xxxxx (errno 105 - No buffer space available)

so i ran top while i restarted daemon in foreground mode. the cpu climbs to 100% and stays there.. once cpu climbs to 90-100% i start seeing the buffer space messages flood and i'm no longer able to access the webui. any ideas on what's going on? this is only ONE torrent running. why is transmission bringing both my cpus to their knees? 8 cores at 2.5ghz should be more than enough for running a single torrent. any help would greatly be appreciated.

[defaut.hostility]

update:
i capped the upload speed to 500 kb/sec and now cpu usage never goes above 1%. when i leave it uncapped, as my upload speed approaches 4mb/sec and above.. this is when transmission goes awol. interesting. any thoughts?
update:
working backwards starting at a upload cap of 5000 kb/sec.. when i got down to cap of 3000 kb/sec. then cpu stayed around 3 to 5% and webui remained working for about 4 minutes before cpu spiked to 30% and webui failed. is transmission not capable of upload connections in excess of 100 and upload speeds in excess of 2-3 MB/sec ?

[defaut.hostility]

changed max upload connections to 35 and left upload speed uncapped. upload speed has reached 6000 kb/sec so far and no issues (i guess i don't REALLY need to be uploading to 100 ppl at once, do i? ) not a single buffer error yet.. 5 minutes and counting... cpu staying between 3 and 7 % memory below 2%. i guess these settings will do.

[Lutin]

Could you please post kB/s instead of kb/s so we can easily compare with our own settings. Thanks.

[defaut.hostility]

those are kB/sec.

[Lutin]

b=bits, B=Bytes.
6000 kb/s = 732 KB/s

http://www.speedguide.net/conversion.php

[defaut.hostility]

oh. i see what you mean now, sorry. when setting caps in settings.json, i was using values like 5000, 3000, which the webui would report upload at 5 or 3 mb/sec.. so if webui is saying its sending 7mb/sec its really only sending 875 kB/sec ? that's disappointing. i might have to go back to another client for seeding. I don't think that is the case though. as the megabyte upload counter seems to be in line with the upload rate counter.