![]() Registered Member ![]()
|
I had got a problem in unlimited connexion mode of ktorrent, it seems to have tonight with a svn of 7days before 2.1rc1 (svn r618630).
I started ktorrent for the night with two finished multifiles seed (set as download I don't know why, cause a stupid .sfv not marked as dl maybe) And 3torrents (popular, ncas and storgate episods). After checking why ktorrent wasn't running anymore, I saw in kernel message that ktorrent have been killed by kernel cause it missed of memory... It hadn't be the first one killed, mysqld passed away first, but the bloody murder chain ended on ktorrent so i suspect it's the responsible of memory out of memory... /var/log/errors show that :
/var/log/warnings show that :
|
![]() Registered Member ![]()
|
I have a mandriva 2007.0, with running :
- apache (small dev website, 5process) - mysql (10tables) - acpid - crond - dm - shorewall (iptables) - dbus - network - ntpd - postfix (local smtpd) - ssh - syslog-ng - udev - wltools With a user kde 3.5.4 session with : - amarok (webradio playing) - konversation (irc) - kopete (msn, jabber) - kcpuload - netmontools - kwikdisk (kdf improved) - kmix - kwallet - kmail - ktorrent (4 instance, include 2preloaded one, with 10tabs for 2 used one) And ktorrent. I growed my user number of file handler limit to this : rapsys soft nofile 2048 rapsys hard nofile 8196 I have 1GB DDR pc3200 memory used that way typicaly : Memory : Disk cache: 36% Disk buffer: 22% Application data: 39% Swap: 42% used If i switch off the swap : Application data: 64% Cache disk: 25% Disk buffer: 6% I just went to check in fact the ktorrent client was put on "high" memory use. |
![]() Moderator ![]()
|
Any idea how much memory it was using ?
Also I wouldn't recommend running with no connection limits, you will just get more and more peers, and there are only so many peers you can download from and upload to. KT will not refuse any connections, so if you have a very popular torrent, and the connections just keep coming in, we will just keep accepting them, until **** happens and you run out of memory. I have seen it happen on torrents with more then 20K peers, that incoming connections just keep coming. |
![]() Registered Member ![]()
|
Any idea to put some security to avoid kernel kill gun fire ?
I mean deal with error of memory allocation and similar. (I remember there are such error in malloc function: try later of example) I think it's good for ktorrent to use all the avaible memory, but that would be great to make it not get out of it... |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Yeah, but ktorrent will be erratic (crash, error, killed) when it hits that limit. I don't understand why you want your KTorrent to be accepting unlimited connections. The Linux networking stack is capable of letting you accept thousands after thousands of connections -- more than you'd possibly ever use -- which will decrease your download efficiency because of BitTorrent protocol overhead chewing up your bandwidth. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]