Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Switeck

Pages: 1 2 [3] 4 5 ... 102
31
Generic / Re: Upload Speeds
« on: September 13, 2019, 04:59:15 AM »
There's a few problems in qBitTorrent (and libtorrent which qBT uses) that prevents very high speeds to single/individual peers and seeds.
uTP support is rather slow and worse has considerable packet loss in my LAN and internet tests.
qBitTorrent (and presumably libtorrent) handles upload slots rather poorly and also seems "reluctant" to connect to peers known to be on the torrent, at least compared to uTorrent.
qBT also can be a bit of a CPU hog at high speeds -- and some of its code is single-threaded so once it maxes out a CPU core ...it won't go any faster.

32
Windows / Re: Remote access and VPN
« on: September 13, 2019, 04:56:01 AM »
If the VPN client on the router still connects to a remote VPN server, the router still wouldn't need to be port-forwarded.

You might need to configure some sort of bridge (rules?) on the router though to get that to work.
VPNs can't be very CPU intensive, and routers tend to have terribly weak CPUs in them, so only try router VPN client as an experiment.

33
MAC / Re: Not able to seed any torrent
« on: September 13, 2019, 04:52:32 AM »
Does your ISP or router firewall your qBitTorrent connection?

Are these torrents marked with the private flag, where connectivity is extremely crippled?

34
Windows / Re: Remote access and VPN
« on: September 11, 2019, 08:53:51 AM »
Yes that's sounds like quite an ordeal. At some point I want to set up my own vpn server as well but Im not there yet. Im planning on starting run the vpn client on the router instead of on the pc, maybe that will generate new problems. It's possible Ive missed something but do you mean I only need to open the port that the VPN server is using? How will the packets know where to go from the vpn port to the web ui port if I don't use port forwarding?
You don't need to port forward to access websites. VPNs are essentially web servers/websites in the same way -- you have a connection TO them and they route packets to you. Port forwarding is only needed for incoming connections.

More is mentioned here:    https://qbforums.shiki.hu/index.php/topic,5085.0.html

35
Windows / Re: Advice on backing up qBittorrent download queue
« on: September 11, 2019, 08:38:40 AM »
Better read these links then:
https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions#Where_does_qBittorrent_save_its_settings
https://qbforums.shiki.hu/index.php/topic,2826.msg13292/topicseen.html#msg13292      Backup qBT settings!

Note: That will only back up the .torrent files and qBT's torrent listing, whether they be seeds, downloading, or queued.
You'll have to back up the contents of the torrents separately.

36
MAC / Re: CPU USAGE
« on: September 10, 2019, 01:17:04 AM »
And windows or a virus/trojan/malware/random power glitch could've corrupted them slightly causing these problems even if you haven't touched the settings.

...That's assuming the cause isn't a bug in qBitTorrent!
If it is a bug, all the more reason to back up the settings and check!

37
Generic / Re: seeds peers
« on: September 10, 2019, 01:14:20 AM »
The numbers in parenthesis are "previously seen" estimates of peers/seeds that might have once been on the torrent even briefly in the last few weeks/months/years.
Those numbers are often bogus, due to bugs in qBitTorrent/libtorrent and other BitTorrent clients...as well as over-counting anything that's either multi-WAN (even having IPv4 and IPv6 at the same time counts) or changes ip addresses sometimes.

The numbers outside the parenthesis are the currently connected (or attempting to connect) peers or seeds.

38
Windows / Re: Remote access and VPN
« on: September 10, 2019, 01:12:00 AM »
Im running Win 10, my VPN client is an app in Windows and im using Windows Defender Firewall and Hardware fw in DD-Wrt running on a Linksys Wrt acm 3200.

I think you need to verify if the port youre using with the web-ui is reachable through your VPN connection. There are lots of sites and tools for that.
It didnt work for me allthough I know I had configured portforwarding correctly in DD-WRT so it was very confusing.

What I think is happening in a lot of cases is that the VPN provider is blocking the port youre trying to use, acting like a second or third firewall.
I'm pretty sure that port forwarding your local router (that's running DD-WRT) would only help if the remote Web-ui is trying to connect through your regular IPv4 ip address and NOT using the VPN's ip address.

This is assuming your VPN connection goes through a VPN server outside your LAN.
Things can be way more confusing if you've got a VPN server of your own -- with multiple starting points and end points both inside and outside your DD-WRT router's LAN.

39
Hiratasuka,

az-calc's settings are based on false assumptions about peer/seed quality dating almost back to the time when 56k dial-up modems were still common.
I've posted about that a few times before on this forum just how awful those settings are.

40
MAC / Re: CPU USAGE
« on: September 05, 2019, 11:41:13 PM »
Back up qBT's settings and .torrent files and reinstall fresh.

If that works, try with just your .torrent files and slowly change qBT's settings till it messes up again...that way maybe the programmers can know what to fix.

41
MAC / Re: CPU USAGE
« on: September 05, 2019, 12:10:28 AM »
It could still be a networking driver issue...but antivirus issues are probably ruled out.

Does any other BitTorrent client (like Transmission on Mac) also show high CPU issues?

42
MAC / Re: CPU USAGE
« on: September 04, 2019, 06:04:45 PM »
Is qbittorrent.exe using most of the cpu, or is the cpu simply overloaded while running qBitTorrent?

Bad drivers or poorly-written antivirus software may have high cpu usage only when qBitTorrent is running.

43
Read this:
https://qbforums.shiki.hu/index.php/topic,5889.0.html
"Windows tool for migration from Bittorrent/uTorrent/Deluge to qBittorrent"

44
While qBitTorrent and some other BitTorrent clients are technically capable of reaching gbit-per-second speeds, as my previous tests show:
https://qbforums.shiki.hu/index.php/topic,3956.0.html

... they generally won't in practice for a lot of reasons.

Here's some things to check:
1.HDDs block speeds -- accessing a spinning platter for data for 100+ peers at once is a huge latency and speed hit that prevents very high speeds. Seeding faster is possible...but it gets expensive! Even a HDD RAID won't help much because of torrents non-sequential accesses and they still have rotational latency no matter how many HDDs are in the RAID. Separate HDDs for multiple torrents probably help more than a consolidated RAID. Fast SSDs would really help, but even Serial-ATA 3 (SATA 3 for short) can possibly get bottlenecked by simultaneous requests. (NCQ support is a must! https://en.wikipedia.org/wiki/Native_Command_Queuing ) A multi-GB sized ramdrive containing the busiest torrents can really help.

2.CPU overloads! Even if the cpu appears to be 75% idle while qBitTorrent is running, it could be that much of qBitTorrent is single-threaded and 1 CPU core (out of 4 total) is maxed out. Intel's CPU hyperthreading makes matters worse instead of better, by converting each real cpu core into 2 virtual cores that cannot share with each other.

3.Upload slots -- fewer (in the ~20-50 range) may be quicker (than 100+) due to lowering HDD accesses and cpu loads.

4.Many reported peers+seeds are not real, and may never been! "Seeds 0(152), Peers 2(19)" If you're connected to only 2 peers, the rest may already be seeds and simply reported as still <100% complete peers. Seeds may have finished uploading and disconnected for good. IP addresses may have changed, some may be multi-homed but limited connectivity on each...so a single peer may get reported 5+ times and only the most recent ip address may work, or not even that if "hopelessly firewalled" (due to NAT, proxy, VPN, etc).

5.Private trackers aggravate these issues further, since DHT, LPD, and PEX are all disabled which prevents most ways of finding other peers+seeds. And tracker update intervals may be MUCH longer than the average peer takes to fully download the torrent, so by the time your BT client even contacts the tracker again the peer is already a seed.

6.BitTorrent protocol has something called uTP which does latency-based checking to determine real-time speeds, but qBitTorrent's implementation of it (in libtorrent's core library to be technical) seems horribly broken and has been that way a long time:
https://github.com/arvidn/libtorrent/issues/1432#issuecomment-284094829
https://github.com/arvidn/libtorrent/issues/3542
Extremely detailed discussion of latency vs speeds:
https://github.com/Tribler/tribler/issues/2620

45
Yes, qBitTorrent can detect changes in files that way...but I don't know if it will truncate the "excess" when it does a force recheck or only when you start download on it again.

Pages: 1 2 [3] 4 5 ... 102