DigiChilli + Shareaza & uTorrent

[Waste]

Hi all,

I have been struggling with Shareaza and uTorrent for a while now on the digichilli network. I am not that clued up to all the settings of both these networks.

Now it seem like (would like to get confirmation about this) GigiChilli is enforcing their bandwith throttling on BitTorrent, P2P networks and HTTP file transfers protocols by delaying the packets (holding them back) or just dropping them??.

I make this assumption because my download manager is reporting very irregular download speeds, as if he gets a few packets in at a reasonable speed, but then don't get a few in for a few milliseconds/seconds, and so on...

On Shareaza this causes some connections/handshakes to timeout and other to go through, this is very bad, as you will lose good connections that way.

Do anyone have advice on how to configure uTorrent, Shareaza and my download manager to handle this type of behaviour?

Or any general advice on this thread on the toppic of how to effectively use these apps on the DC network, but not doing bad things like encapsulating them in HTTP packets.

Dave specifically complained about a certain behavior that was causing problems.

PS. I appreciate their QoS, as this allow reasonable web browsing although I'm downloading... nice work.

Bernard

 

[froot]

If you have issues with timeouts, check your program's preferences for timeouts.... you can set the time that it allows before throwing a timeout.

I have the same issue with FTPs..... I'm a web developer and am not able to do FTP transfers on my digichilli account because of the timeouts......

Running your torrents as an http service doesn't always work if the ISP knows how to take care of that.... it's just one of those things.

 

[Waste]

I haven't tried my account at FTPing, although I'm also a developer. I have a 4Mb line, but uses the Mild DC account, so I just keep it just for downloading. Their is a lot more to play with than just the timeouts, I have increased them, but maybe if I open more download connections to the server, lets say 4 connections (using download manager) it will improve as each connection would randomly have timeouts, but because 4 are running they will constantly be downloading...

In other words if you have 256kbps to work with:
1 connection @ 256kbps, may be worse than,
4 connections @ 64kbps, just because with the one connections the download 1 second then delay one second...

/^^^^\____/^^^^\____

where the 4 connections would run at constant 64kbps that are more accurate like:

/-------------------------\

in the end the only thing that will be better is the ETA, will be accurate, it will probably download the same duration but without the spikes in the graphs.

Lol, don't even know if this is worth my brain power .