IRC versus FTP and HTTP tests

G

guest2013-1

guest
Joined
Aug 22, 2003
Messages
19,800
Reaction score
13
IRC, never more than 11kb/s very unstable download, usually averages 9.5kb/s sometimes down to 2.9kb/s... as I said, VERY unstable. This is for both upload and download, upload is a bit more stable @ around 8-10kb/s

Same server (and no, this server is located in the good ol' USA), FTP (upload) constant 25.6kb/s (or sometimes 25kb/s)

Didn't test downloads on FTP server.

HTTP server (same PC, only with directory browsing installed with IIS) Average 66kb/s, spikes up to 75kb/s and never drops below 45kb/s

This is the SAME server, just on different protocols.

Now, tell me again how Sentech DOES NOT do port prioritization? Please, i want to kick you in the nuts..... please... come... someone tell me how they're not doing this.... please, my foot is all warm and fuzzy to go........ go ahead... make my day
 
I heard from a friend in jhb that his Bit Torrent Never goes green. It stays on yellow(Behind a proxy or firewall). He says that he isn't behind anything. Can you check if you have the same problem?

..- dot dot dash ;)
 
No idea what you mean by "his bit torrent never goes green"

All i know is bit torrent is no measure for ANY sort of download/upload ratio speeds. However, 8kb/s up (i set it to that) and I average 30kb/s downstream, but remember, this is spikes of up to 77kb/s and sometimes I crawl at 2kb/s, obviously, all depending on who is seeding etc, thats why torrents is not my preferred means of getting what i want (whatever it is you police looking dudes you!)
 
Noone, Sentech might not be shaping traffic, but I know for a fact that a lot of OTHER isp's DO. So it could very well be someone along the way to that IRC/FTP server of yours that is shaping traffic on a router along the way. This is the internet.

There are no guarantees. If you want to do a proper test, try DCC'ing something from someone local, to see if there's any prioritisation. Take the same file, via ftp, irc, and http from the same person, under the same conditions. Then you have an empirical test.


<center><h5><font color="red">Oo. MyWireless <s>Hacks</s> Tweaks & Tech Info.oO </font id="red"></h5></center>
 
Dude, i did just that, and I went to an overseas buddy of mine to test it as well

IS could be the culprit
 
Which do you think are prioritised? Indicate for IRC/DCC/Kazaa/HTTP/BitTorrent

The colors mentioned are for the status lights in the bittorrent client software. The best client is at http://bt.degreez.net
 
IS *do* shape traffic to and from non IS customers. Like iff you download off ftp.is.co.za from outside their AS you will not get more their 10KBps

<hr noshade size="1">
Very funny Scotty. Now beam down my pants!!
 
Oh

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">This is the SAME server, just on different protocols.

Now, tell me again how Sentech DOES NOT do port prioritization? <hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

It's called crapy protocols.

<hr noshade size="1">
Very funny Scotty. Now beam down my pants!!
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by noone</i>
<br />
Now, tell me again how Sentech DOES NOT do port prioritization? Please, i want to kick you in the nuts..... please... come... someone tell me how they're not doing this.... please, my foot is all warm and fuzzy to go........ go ahead... make my day
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

OK, Sentech does NOT do port prioritization.
You theory is flawed..since IRC DCC transfers can use ANY port it wishes. So tell me now HOW can they do port prioritization if there's not a set port that DCC use?

--
 
DCC goes through port 59 if i'm not mistaken, you reckon I should try changing that?

hmmmm
 
Cant some MyWi users just prove this true or false once and for all. Just say whether you get more than 10k/bytes second using IRC so we can be sure that its not just one user and also to stop everyone from thinking he is stupid or something when that is most probably not the case.

I personally havent seen anything other than the yellow light for bittorrent and also no speeds above 6k (havent tested much). I havent used anything above 128k so I wouldnt know of any problems yet with IRC.

As I am considering upgrading later on to 256 this is a valid concern.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by greedyflyza</i>
<br />Cant some MyWi users just prove this true or false once and for all.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

I would, but I don't IRC


<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
<i>From http://www.irchelp.org/irchelp/rfc/ctcpspec.html</i><br />
Initiator:
DCC command issued.
Create a socket, bind it to INADDR_ANY, port 0, and
make it passive (a listening socket).
Send the recipient a DCC request via CTCP supplying
the address and port of the socket. (This
is ideally taken from the address of the local
side of the socket which is connected to a
server. This is presumably the interface on
the host which is closest to the rest of
the net, and results in one less routing hop
in the case of gateway nodes).
Continue normally until a connection is received.

On a connection:
Accept the connection.
Close the original passive socket.
Conduct transaction on the new socket.

Acceptor:
CTCP DCC request received.
Record information on the DCC request and notify the user.

At this point, the USER should be able to abort (close) the
request, or accept it. The request should be accepted with
a command specifying the sender, type, and argument, or
a subset of these where no ambiguity exists.

If accepted, create a TCP socket.
Connect the new socket to the address and port supplied.
Conduct the transaction over the socket.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

As you can see...any port. noone, try using a smaller block size (smaller than the MTU, try using 1024).
If I remember correctly in MIRC you set the port of the DCC server. Trying changing that then...


--
 
it was on 2048, changed it to 8192, doubt a smaller block size will work, but I'll try that.

It's just strange, i can upload 25kb/s no problem, gimme an FTP and I'll do it, but through IRC, I can only do 10kb/s, so what I did is I tried sending two files at once, and boom, both sent at 10kb/s constantly.

It's a shame the receive doesn't work the same way, seems that if I receive more than one file, my 10kb/s gets split into two instead of just increasing to a total of 20kb/s downstream (which would be ideal, because then I can receive 5-7 files at one time @ 10kb/s)

Maybe it is IS? I'll do some more tests and let you know
 
goto irc.tveps.net and join #southpark-episodes

remember, i'm on the 512k package
 
the local ones have dissapeared dude, for some reason they prefer torrents now

sucks ass ;)
 
gimme some more international ones, that other one is kinda limited to what they have, oh crap it 7:50 im gonna be late for campus.

..- dot dot dash ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X