Custom Query (2447 matches)

I've tried the 1.0 RC5 and RC7 releases on Ubuntu Hardy and both result in the same problem:

1) upload and download speeds of deluge are extremely slow. Download stays below 100 kb/s while it was well above 1000 kb/s with the 0.5.x series. Downloading multiple torrents at the same time also seems to reduce the average download speed compared to only having one active torrent (all though I can't prove that).

2) when deluge is active it also seems to cause networking issues for the rest of the applications. Pidgin (all protocols) and Skype regularly disconnect, evolution times out connecting to mail servers and browsing using Firefox is almost impossible. Firefox takes forever to connect to a site, times out, or when it does load a page it takes a long time and then suddenly the entire page appears (in stead of rendering whatever is already received).

I've added a screenshot of the Gnome System Monitor. Even though the interface is in Dutch, you'll probably find the bottom graph (showing networking activity) interesting. This was taken just after logging in, with no real other networking activity going on other than Deluge downloading and seeding. Average downloading was probably about 75 kb/s at that time. Please let me know if you need any additional information.

Thank you for the (other than this issue) great software by the way!

Tom

Problem : Version 1.0.0_RC7 segfaults when trying to add a corrupted torrent. What's expected : At least not segfaulting. A better way would be to display a message like in version 0.5.9.4.

Bitcomet creates (if user wishes to do so) padding files.

Their name is like this:

  _____padding_file_599_if you see this file, please update to BitComet 0.85 or above____
  _____padding_file_12_if you see this file, please update to BitComet 0.85 or above____

etc.

Their purpose is to adjust file start to a new chunk. Their content is 0x00 straight away (afaik) of their size. This is insane as those files can make the torrent size grow about 5-10%. They are a waste of Bandwith.

Therefore:

• Automatically fill them with 0x00 and mark them as 100%, so you do not get to much overhead (which is about 5-10% ! ).
• Also make them invisible in files list (or maybe a checkbox)
• Mark them as "do not upload" or "low priority upload".

I marked this as major as I think it should be quite easy to implement. Also, this makes a major difference in both bandwith usage AND usability.

Reference: ​http://en.wikipedia.org/wiki/BitComet#Padding_Files

Regards