Recent Posts

Pages: 1 ... 8 9 [10]
Windows / Re: Regular crashes in 4.1.4
« Last post by coolio2013 on December 02, 2018, 01:33:18 AM »
4.1.4 also for me is really bad, nearly unusable. It crashes out of the blue sky, more often than 4.1.3 (which also crashed often, but not that frequently). Nearly thought I'm the only one... but there are no more reports on github (crash info can't be read and is white usually, so I can't help).

It does not matter if rechecking is running or not (uses a LOT of mem). 1.2G of mem seems to be a threshold, above and it will crash for sure (I'm using Win 32bit).
Also annoying after a new start: 4.1.4 does not remember states: previously paused will be rechecked. And 'downloading metadata' will get state paused.
Date for 'Added' is wrong, this may is set to the date if paused/downloading metadata...

If there is no fix for the crashes, I may have to dispose off qbt, because this is one of the last versions I could use.
Windows / Re: Basic Torrent Questions - Connection - Queuing.
« Last post by Vectraat on December 02, 2018, 01:31:50 AM »
Uh ok, that was a bit much for me. Was hoping for a simpler cliff notes explanation. I do appreciate the effort though.

My connection is 300/300

What numbers would you recommend for for "Number of Connections" ? I left the default values...
-Global maximum number of connections: 200
-Maximum number of connected peers per torrent: 50
-Number of upload slots per torrent: 4

For Queuing - "Maximum number of active torrents (upload or download)" should be what?
I'd think you wouldn't want too many at the same time as that may wear down the disk quicker and slow down your upload across torrents? 
Windows / Re: Regular crashes in 4.1.4
« Last post by saywhat on December 01, 2018, 10:19:39 PM »
1.Lots of torrents in qBT?

2.Many torrents recently added?

3.Torrents stored on an external HDD that may not be active when qBT tries to access it?

4.Using a VPN or proxy?

5.qBT's cache set too large? (32bit crashes if set over ~1000 MB)

Thanks for the reply...

1. There was 267, now 200 so I've lost some in the crash...thanks Qbittorrent...gigs of downloads gone!

2. Not really I add about 40 each week but others get removed so it stays sort of static (in total torrent numbers)

3. Yes, been there done that, but not this time.

4. Yes a VPN.

5. I'm on 64 bit win 7

However, I am doing nothing different than I've beeen doing for a couple of years. The only difference is the latest and previous versions of Qbittorrent I've been using which is when the crashes started.
MAC / Re: [UNOFFICIAL] qBittorrent 4.1.4 for macOS
« Last post by victorhooi on December 01, 2018, 09:28:33 PM »
This doesn't work for me on MacOS Mojave:

Code: [Select]
Process:               qbittorrent [1021]
Path:                  /Applications/
Identifier:            org.qbittorrent
Version:               4.1.4 (0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           qbittorrent [1021]
User ID:               501

Date/Time:             2018-12-02 07:26:49.941 +1100
OS Version:            Mac OS X 10.14.2 (18C52a)
Report Version:        12
Bridge OS Version:     3.0 (14Y674)
Anonymous UUID:        949068F0-44FF-FAF2-BCA7-FC2F0F24A0FB

Time Awake Since Boot: 1100 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @loader_path/libboost_system-mt.dylib
  Referenced from: /Applications/
  Reason: image not found

Binary Images:
       0x103727000 -        0x103e0fff7 +org.qbittorrent (4.1.4 - 0) <8FD8529B-2E49-371C-9A15-2D321A4C89FB> /Applications/
       0x103f54000 -        0x1041f7fff +libtorrent-rasterbar.9.dylib (0) <CF58FF72-93B4-3852-A169-D95CE64A44F8> /Applications/
       0x104257000 -        0x104258fff +libboost_system.dylib (0) <BCC5B0B6-C620-329A-AC42-B42CC625CB7E> /Applications/
       0x104262000 -        0x104295fff +org.qt-project.QtSvg (5.11 - 5.11.2) <E4052D2C-1CB1-3F2B-B488-81009FC4018D> /Applications/
       0x1042b3000 -        0x1046ebfff +org.qt-project.QtWidgets (5.11 - 5.11.2) <81AB1FEE-3D0E-34F3-B85C-945687EEA587> /Applications/
       0x104850000 -        0x104c81fef +org.qt-project.QtGui (5.11 - 5.11.2) <47E8ACE2-9967-3CA7-BFF9-8B1FC513C782> /Applications/
       0x104d7c000 -        0x105281ff7 +org.qt-project.QtCore (5.11 - 5.11.2) <B0E48172-ED70-3ACE-B648-738524DD6AD9> /Applications/
       0x10533b000 -        0x105343ffb +org.qt-project.QtMacExtras (5.11 - 5.11.2) <639E20FD-CC6E-37AC-A0C0-0C3616E40821> /Applications/
       0x10534d000 -        0x10544dff7 +org.qt-project.QtNetwork (5.11 - 5.11.2) <0550946D-1C98-3539-839A-C09D37EC70D6> /Applications/
       0x105496000 -        0x1054c7fff +org.qt-project.QtXml (5.11 - 5.11.2) <896E9316-0A25-3B27-B71D-49526E0D1D00> /Applications/
       0x1054de000 -        0x10551eff7 +libssl.1.0.0.dylib (0) <0939E9FE-CAF8-3E1B-8635-15C0FD7D13CD> /Applications/
       0x10553c000 -        0x10568fe97 +libcrypto.1.0.0.dylib (0) <A6F555BF-9F61-3BC9-9488-4E267E29E718> /Applications/
       0x1056fc000 -        0x1056fffff +libboost_chrono-mt.dylib (0) <7FF427B9-D5E8-37EC-AD6F-099BA3D10AA8> /Applications/
       0x105703000 -        0x105706fff +libboost_random-mt.dylib (0) <D4DF0E08-C8AB-3363-8B46-B854FB34B6C2> /Applications/
       0x109cbb000 -        0x109d39a67  dyld (640.2) <9055ED89-4099-3B32-B601-75E4973C5E1A> /usr/lib/dyld
    0x7fff45450000 -     0x7fff45454fff (3.3.2 - AGL-3.3.2) <19EFBFB3-83C7-3E09-93C9-DE2BF4336102> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff46a66000 -     0x7fff47887ffb (6.9 - 1671.20.108) <790C5DA5-7521-327E-BA49-8E5ADD10E808> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff487b7000 -     0x7fff487b7fff (158 - 158) <87D26CA2-ADDB-3E03-BA19-F651BE02A010> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff494f5000 -     0x7fff49942ff7 (6.9 - 1561) <F2D956F3-CCD3-3293-B381-324038D3B417> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff4a7b2000 -     0x7fff4a7b2fff (941 - 941) <2D2F6EEF-C150-3E06-AB2F-BE50DDF200C9> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff4b6ac000 -     0x7fff4b6b1fff (2.7 - 2.7) <97707A79-30E7-3D99-AA20-B992B0900BC4> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff4b87a000 -     0x7fff4bc48fff (6.9 - 1561) <B8717846-A28C-3609-8CE2-6DB5C2FDCA39> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff4bf6f000 -     0x7fff4c001ff7 (2.0.2 - 1483.230.1) <A8F45B2F-423C-3674-B9E1-81CB4B25F3F8> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff53677000 -     0x7fff53686ff3 (17.3.1 - 17.3.1) <61B69CE5-615C-332A-A144-80FF77276279> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff73bdf000 -     0x7fff73be0ffb  libSystem.B.dylib (1252.200.5) <955FCEAB-EC63-37B0-A9DB-4884FD84BCB6> /usr/lib/libSystem.B.dylib
    0x7fff73e39000 -     0x7fff73e90ff7  libc++.1.dylib (400.9.4) <B260AC33-EB9A-30C6-8746-D011B3B02B08> /usr/lib/libc++.1.dylib
    0x7fff73e91000 -     0x7fff73ea6fff  libc++abi.dylib (400.17) <446F4748-8A89-3D2E-AE1C-27EEBE93A8AB> /usr/lib/libc++abi.dylib
    0x7fff75686000 -     0x7fff75e0cfe7  libobjc.A.dylib (750.1) <804715F4-F52D-34D0-8FEC-A25DC08513C3> /usr/lib/libobjc.A.dylib
    0x7fff76569000 -     0x7fff7657bffb  libz.1.dylib (70.200.4) <15F7B40A-424C-33BB-BF2C-7E8195128B78> /usr/lib/libz.1.dylib
    0x7fff765ec000 -     0x7fff765f0ff3  libcache.dylib (81) <704331AC-E43D-343A-8C24-39201142AF27> /usr/lib/system/libcache.dylib
    0x7fff765f1000 -     0x7fff765fbff3  libcommonCrypto.dylib (60118.220.1) <9C865644-EE9A-3662-AB77-7C8A5E561784> /usr/lib/system/libcommonCrypto.dylib
    0x7fff765fc000 -     0x7fff76603fff  libcompiler_rt.dylib (63.4) <817772E3-E836-3FFD-A39B-BDCD1C357221> /usr/lib/system/libcompiler_rt.dylib
    0x7fff76604000 -     0x7fff7660dff3  libcopyfile.dylib (146.200.3) <5C5C4F35-DAB7-3CF1-940F-F47192AB8289> /usr/lib/system/libcopyfile.dylib
    0x7fff7660e000 -     0x7fff76692fdf  libcorecrypto.dylib (602.230.1) <C78D1A87-5543-3561-BEB4-3B480BA94ECB> /usr/lib/system/libcorecrypto.dylib
    0x7fff76719000 -     0x7fff76753ff7  libdispatch.dylib (1008.220.2) <2FDB1401-5119-3DF0-91F5-F4E105F00CD7> /usr/lib/system/libdispatch.dylib
    0x7fff76754000 -     0x7fff76783ff3  libdyld.dylib (640.2) <B0562053-850C-306A-B12F-CA25DFE5CD9E> /usr/lib/system/libdyld.dylib
    0x7fff76784000 -     0x7fff76784ffb  libkeymgr.dylib (30) <A4EFD9A4-2EF3-3E18-B325-F527E3821939> /usr/lib/system/libkeymgr.dylib
    0x7fff76792000 -     0x7fff76792ff7  liblaunch.dylib (1336.220.5) <4D60667C-DD62-398D-B2B9-5BCA0F13D61B> /usr/lib/system/liblaunch.dylib
    0x7fff76793000 -     0x7fff76798fff  libmacho.dylib (921) <6ADB99F3-D142-3A0A-B3CE-031354766ACC> /usr/lib/system/libmacho.dylib
    0x7fff76799000 -     0x7fff7679bffb  libquarantine.dylib (86.220.1) <58524FD7-63C5-38E0-9D90-845A79551C14> /usr/lib/system/libquarantine.dylib
    0x7fff7679c000 -     0x7fff7679dff3  libremovefile.dylib (45.200.2) <BA53CA8A-9974-3A43-9265-B110B1AE470F> /usr/lib/system/libremovefile.dylib
    0x7fff7679e000 -     0x7fff767b5ff3  libsystem_asl.dylib (356.200.4) <33C62769-1242-3BC1-9459-13CBCDECC7FE> /usr/lib/system/libsystem_asl.dylib
    0x7fff767b6000 -     0x7fff767b6fff  libsystem_blocks.dylib (73) <152EDADF-7D94-35F2-89B7-E66DCD945BBA> /usr/lib/system/libsystem_blocks.dylib
    0x7fff767b7000 -     0x7fff7683ffff  libsystem_c.dylib (1272.200.26) <D6C701A2-9F17-308D-B6AC-9E17EF31B7DF> /usr/lib/system/libsystem_c.dylib
    0x7fff76840000 -     0x7fff76843ff7  libsystem_configuration.dylib (963.200.27) <94898525-ECC8-3CC9-B312-CBEAAC305E32> /usr/lib/system/libsystem_configuration.dylib
    0x7fff76844000 -     0x7fff76847ff7  libsystem_coreservices.dylib (66) <10818C17-70E1-328E-A3E3-C3EB81AEC590> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff76848000 -     0x7fff7684effb  libsystem_darwin.dylib (1272.200.26) <07468CF7-982F-37C4-83D0-D5E602A683AA> /usr/lib/system/libsystem_darwin.dylib
    0x7fff7684f000 -     0x7fff76855ff7  libsystem_dnssd.dylib (878.230.2) <F603B1CF-E467-3C50-830A-785D1A8D9F07> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff76856000 -     0x7fff768a2ff3  libsystem_info.dylib (517.200.9) <54B65F21-2E93-3579-9B72-6637A03245D9> /usr/lib/system/libsystem_info.dylib
    0x7fff768a3000 -     0x7fff768cbff7  libsystem_kernel.dylib (4903.231.4) <B546DE30-393C-3BD7-BD37-E1ADFA270321> /usr/lib/system/libsystem_kernel.dylib
    0x7fff768cc000 -     0x7fff76917ff7  libsystem_m.dylib (3158.200.7) <AF25F8E8-194C-314F-A2D3-A424853EE796> /usr/lib/system/libsystem_m.dylib
    0x7fff76918000 -     0x7fff7693cff7  libsystem_malloc.dylib (166.220.1) <4777DC06-F9C6-356E-82AB-86A1C6D62F3A> /usr/lib/system/libsystem_malloc.dylib
    0x7fff7693d000 -     0x7fff76948ff3  libsystem_networkextension.dylib (767.220.1) <74818C3D-9B68-3823-A737-6A4B782618F2> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff76949000 -     0x7fff76950fff  libsystem_notify.dylib (172.200.21) <65B3061D-41D7-3485-B217-A861E05AD50B> /usr/lib/system/libsystem_notify.dylib
    0x7fff76951000 -     0x7fff7695afef  libsystem_platform.dylib (177.200.16) <83DED753-51EC-3B8C-A98D-883A5184086B> /usr/lib/system/libsystem_platform.dylib
    0x7fff7695b000 -     0x7fff76965fff  libsystem_pthread.dylib (330.230.1) <C48DC91E-EDC8-31E4-B0F6-5968ECA8797C> /usr/lib/system/libsystem_pthread.dylib
    0x7fff76966000 -     0x7fff76969ff7  libsystem_sandbox.dylib (851.230.3) <B20516CF-71A7-3161-9FB8-B85B26D7BFD7> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff7696a000 -     0x7fff7696cff3  libsystem_secinit.dylib (30.220.1) <5964B6D2-19D4-3CF9-BDBC-4EB1D42348F1> /usr/lib/system/libsystem_secinit.dylib
    0x7fff7696d000 -     0x7fff76974ff7  libsystem_symptoms.dylib (820.237.2) <487E1794-4C6E-3B1B-9C55-95B1A5FF9B90> /usr/lib/system/libsystem_symptoms.dylib
    0x7fff76975000 -     0x7fff7698aff7  libsystem_trace.dylib (906.220.1) <4D4BA88A-FA32-379D-8860-33838723B35F> /usr/lib/system/libsystem_trace.dylib
    0x7fff7698c000 -     0x7fff76991ffb  libunwind.dylib (35.4) <EF1A77FD-A86B-39F5-ABEA-6100AB23583A> /usr/lib/system/libunwind.dylib
    0x7fff76992000 -     0x7fff769c2fff  libxpc.dylib (1336.220.5) <30B2E6ED-B4CC-3171-8C2E-F03A924C3969> /usr/lib/system/libxpc.dylib

Model: MacBookPro13,3, BootROM, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.38f7
Graphics: Intel HD Graphics 530, Intel HD Graphics 530, Built-In
Graphics: Radeon Pro 450, AMD Radeon Pro 450, PCIe
Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 ( AirPortDriverBrcmNIC-1305.2)
Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: USB 10/100/1000 LAN, Ethernet, en8
USB Device: USB 3.0 Bus
USB Device: iBridge
USB Device: USB 10/100/1000 LAN
Thunderbolt Bus: MacBook Pro, Apple Inc., 39.3
Thunderbolt Bus: MacBook Pro, Apple Inc., 39.3

Windows / Re: Regular crashes in 4.1.4
« Last post by Switeck on December 01, 2018, 08:41:18 PM »
1.Lots of torrents in qBT?

2.Many torrents recently added?

3.Torrents stored on an external HDD that may not be active when qBT tries to access it?

4.Using a VPN or proxy?

5.qBT's cache set too large? (32bit crashes if set over ~1000 MB)
Windows / Regular crashes in 4.1.4
« Last post by saywhat on December 01, 2018, 07:45:05 PM »
OS Win7

Getting crashes, about two a day, in 4.1.4 and also was the same in the previous version whatever that was. Never had crashes before of any sort. Not doing anything with Qbittorrent when it crashes as it is running in the background while I'm working on other stuff. Qbittorrent window goes all white and I get the Windows crash report as follows:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   qbittorrent.exe
  Application Version:
  Application Timestamp:   5bf5ae83
  Fault Module Name:   qbittorrent.exe
  Fault Module Version:
  Fault Module Timestamp:   5bf5ae83
  Exception Code:   c00000fd
  Exception Offset:   000000000012246e
  OS Version:   6.1.7601.
  Locale ID:   2057
  Additional Information 1:   e7b1
  Additional Information 2:   e7b1ac266b66f808e0dd08e04a4eeefe
  Additional Information 3:   be85
  Additional Information 4:   be85b69551f4c788771d73128e6aa070

Windows / Re: Basic Torrent Questions - Connection - Queuing.
« Last post by Switeck on December 01, 2018, 06:55:53 PM »
a) No, "Global Maximum number of connections" is the max number of peers + seeds (and a few other ip connections) to allow at once. Setting it too high can overload slow internet connections, unstable networking (due to faulty network drivers/routers/modems), or contended/congested/poor wifi. It may need to be as low as 20-100 for slow broadband connections or bad networking conditions and almost everything else will need to be a smaller number than that.

b) Maximum number of connections per torrent is pretty much the max peers + seeds to allow to connect to your torrent at once. Even ridiculously fast internet connections, like 10 gigabits/second might be better off with that number set lower. I recommend 50 while downloading for internet connections with less than 100 mbit/sec upload and only 10 connections per torrent while only seeding (after all downloads have completed -- because seeds don't need to stay connected to other seeds).
EACH torrent typically needs 4-10 max connections allowed to run smoothly, so setting max connections to just 5 won't work well for 5 simultaneous downloads at the same time -- even if each torrent only got 1 peer or seed connection, those could be very slow or "dead" ones! (I mean dead ones in the sense that they give nothing and refuse to download from your end.)

It's easier to answer d) first, so...
d) "Inside" the Maximum number of connections per torrent is "Maximum number of upload slots per torrent". A really busy downloading torrent may be connected to 100 peers+seeds, say 50 of each. But it can only upload to the peers, since the seeds already have 100% of the torrent. "Maximum number of upload slots per torrent" limits the number of peers to upload to at once PER torrent, like only 10 of them -- so that means at any given moment qBitTorrent might be uploading to 0-10 of the 50 peers and NOT uploading to 40-50 of those peers. Only the peers qBitTorrent is (or has in the last 10 minutes) encouraged to upload BACK to you to return the favor -- it's a core rule of the BitTorrent protocol and makes "giving more to others" worthwhile. By limiting "Maximum number of upload slots per torrent" to LESS than max peers, only those peers that have given you the MOST consistently get to download from you...encouraging them to give MORE.

c) Just as uploading to every peer at once on a torrent is a bad idea if you have really busy torrents, uploading to every peer on every torrent is a really bad idea. So "Global maximum number of upload slots" can limit that to far less -- even to the point that if it's LESS than "Maximum number of upload slots per torrent" then the lower global upload slot limit will limit 1 busy torrent from uploading to more peers.

Here's where the "math gets ugly":
The numbers of all 4 settings depend entirely on maximum usable/sustainable upload speed -- and to a lesser degree also max usable download speed while downloading torrents.
Too many connections and upload slots, globally or per torrent, can REDUCE download and upload speeds immensely.
Too few can also REDUCE download and upload speeds immensely!
This even depends on how many active torrents you have, how active each torrent is, and how fast the peers/seeds are on those torrents.
Private trackers often tend to have faster-on-average peers+seeds -- you won't see very many slow DSL peers+seeds there!
Slow DSL peers+seeds are unlikely to be able to upload even 100 KiloBYTES/second in their BitTorrent clients because they often only have 0.1-1 megabits/second upload bandwidth.
Even cable ISPs often only give 1-50 megabits/second upload bandwidth -- with 10-20 mbit/sec being "typical best", which only works out to be about 1-2 MegaBYTES/second usable upload bandwidth assuming nobody else is sharing that service. 4+ people in 1 household are going to be rather upset with a BitTorrent uploader that tries to upload at 80+% of max upload speed 24/7! (likewise if at >80+% of max download!)

So for example, with 100 KB/sec max usable upload speed (assuming 1 mbit/sec usable upload bandwidth) ...I'd use these values:
"Global maximum number of upload slots" SHOULDN'T be higher than 20 ever -- because that works out to be only 5 KB/sec upload speed (56k dial-up modem speeds) per upload slot (100/20) and probably would work better if only 5-10. Other peers will typically only upload back to your peer if you're uploading to them as fast or faster than what peers are giving to them, so setting this "wrongly" can mean uploading a whole lot and almost no peers give anything back!

"Maximum number of upload slots per torrent" depends on how many torrents you want active at once -- each needs at least 2 upload slots, so that put a max active torrents at once of 10 (with 20 max global upload slots.) Torrents will do a little better with 3-5 max upload slots per torrent -- uploading to at most 3-5 peers at once.

"Global Maximum number of connections" depends on max usable download speed as well as max sustainable upload speed. If you can download at 1 MegaBYTE/second (10x upload speed's 100 KB/sec), then even 30 global max connections is sufficient and 50 likely to be overkill. But if you can download at 3+ MegaBYTES/second and/or on lots of public torrents with slow peers+seeds, then 50-200 global max connections may work a little better. (Only a little better because each slow peer/seed may give nothing, so 100+ more peers/seeds that give nothing won't increase DL or UL speeds.)

Even seemingly idle peers+seeds are sending/sharing Peer EXchange (PEX) lists of ips for other peers/seeds on the same torrent (on public torrents anyway), HAVE torrent piece messages (for what parts of the torrent they have, to compute and update their percent complete), download/upload requests (typically including requested piece lists), tracker exchange (if enabled, it's a bad idea to use due to poisoning attacks and similar/duplicate trackers), possibly Local Seed Discovery (seeing if peers/seeds are on the same LAN as yours so they can ignore normal max speed limits, which can cause massive lag if incorrectly considered "local"), and lastly "hey I'm still here" TCP/IP Keep-Alive messages (to avoid their connection from being broken due to inactivity).
All that activity costs bandwidth and speed, especially with 100's of connected seeds+peers at once!

Maximum number of connections per torrent needs to be equal or greater than max upload slots per torrent, perhaps 2-5x greater if you're mainly going after torrents that have far more seeds than peers or if most peers are really slow. Private trackers won't need as many connections because most of the time is spent seeding and even 10 seeds on 1 torrent can max out download speed.
Max number of connections per torrent also needs to be lower or equal to Global max connections. (Equal if only 1 torrent is allowed to run at a time.)

A weird problem with max connections per torrent is peers can get "mad" if you don't download OR upload to them within ~5-10 minutes of connecting to them. These peers may auto-ignore or even auto/manual ban or at least disconnect your peer/seed after that time. So having a lot of connections that aren't used on a torrent that takes a long time to download or seed can mean they start ignoring your end -- refusing to upload OR download! After that time, your peer could upload a lot to them and they would still refuse to "give" upload back because they've already ignored/snubed your peer for giving them nothing earlier. They may also auto-disconnect from your peer/seed "due to inactivity" which can often result in them connecting and disconnecting over-and-over again many times in an hour...with each reconnect slowing everything else down slightly, especially if BitTorrent encryption is used (which makes the initial connection handshake negotiation process use far more bandwidth).

Beyond this, there can be some "overlap" where 1 torrent is allowed more than its "fair share" of max connections or upload slots from the global max supply.
So if global max connections is 100, it's ok for 1 torrent to be allowed a max of 20-50 connections even if there's 5-10 other torrents active -- assuming most of the other torrents are seeding and only have 0-5 peers connected at a time.
Same with global max upload slots. 1 torrent could have a max of 5 upload slots out of the 10 total so long as there's no more than 5 other seeding torrents active (which get 1 upload slot each).

Don't run too many torrents at once, especially busy ones, or your download/upload speeds from/to peers+seeds can be very slow!
10 active torrents with 50 peers or seeds each could be 500 total connections -- so might be better to limit to only 5 active torrents with 20 max connections each (5-10 while seeding) for 100 max global/total connections.

Doubling max usable upload and download speed does not mean max connections and max upload slots can be also doubled. Law of diminishing returns quickly apply, so it takes more like 10x as much upload/download speed to merit doubling max connections/max upload slots!
Windows / Re: Failure to connect after suspend
« Last post by AndyHenderson on December 01, 2018, 05:47:56 PM »
An even simpler solution would be to retry, say, 5 times with, say, 10 seconds between each retry when getting an error trying to read the feed. As it stands QB tries just once and gives up.

Windows / Basic Torrent Questions - Connection - Queuing.
« Last post by Vectraat on December 01, 2018, 05:25:52 PM »
Under "Options" --> "Connection" -->  Connection Limits.

a.) Is "Global Maximum number of connections" the amount of people who can download from you at the same time? So if I only wanted 5 simultaneous downloads at the same time, I'd just set 5 instead of 500? How is this different from Torrent Queuing --> Maximum active downloads/uploads?

b.) Maximum number of connections per torrent. Currently set to 100, but I don't see why I wouldn't want to max this?

c.) What is "Global maximum number of upload slots" ?

d.) What is "Maximum number of upload slots per torrent" ?

Windows / Re: Unable to add search engines
« Last post by [email protected] on December 01, 2018, 03:48:30 PM »
I have the exact same problem. Any plugins I can find, has the same result when trying to install them: "...not supported...".
This is after I have formatted my desktop disks, and started to reinstall all apps. Before formatting, I was using some Qbit version starting with 4.1.X, without problems. Then I also formatted another desktop, and found no problem when re-installing the latest Qbittorrent version.
The only difference was that the one that works, is a W7Ultimate version of windows o/s, and the the one that does not work, is a windows W10Pro version. I then uninstalled Qbittorrent and re-installed a version 3.x.x of it. That also did not get the plug-ins to install. Same message of " ... not supported...". I then upgraded it to the latest version of qbittorrent, but still the plug-ins would not work.
Can anyone help?
Pages: 1 ... 8 9 [10]