I was wondering if anyone is having issues with Nocster/BurstNET.

I am only able to get a sustained transfer of around 150kbps (~19Kbps) to them, which i feel is very slow.

I am performing a backup and at this rate it will take several hours to download a relatively small file.

From other datacenters I am able to sustain transfers over 2000kbps so it is not a problem on my end.

Hello,

I'm obviously not a nocster customer, but you may want to contact them/open a ticket to have them check the duplexing on both your switch port and the server. Other than network congestion, this is typically the leading cause of very slow transfers. For example, the switch may be set at half-duplex while the server is set at full-duplex.

Hope that helps!

well... i doubt that might be the problem but it could be anything i suppose.

may i ask how i could check what the duplex settings are on the server before i submit a ticket?

thanks.

You can use the 'ifconfig' command from a shell on your server to see what the NIC settings are for your machine. Doing this on one of my machines includes this line:

media: Ethernet 100baseTX <full-duplex>

This means it is running at 100Mbps full-duplex. Full-duplex is what you want. In lay terms, full-duplex creates 2 separate paths which aren't shared--one for inbound traffic, one for outbound traffic. This server could push 100Mbps outbound, while pulling 100Mbps inbound at the same time. Half-duplex is more of a "one lane road." A half-duplex connection at 100Mbps can only handle a total inbound+outbound of 100Mbps--40 in, 60 out, as an example.

The problem with this is I'm betting you'll need your provider's involvement to query the settings on the switch, as you wouldn't have the ability to do this.

i had actually run the ifconfig command when you first suggested the duplex issue. it doesn't output what you give, but i have other systems and they don't output "media: Ethernet 100baseTX <full-duplex>" either.

so i don't think it's a duplex issue. besides, what kind of hardware only uses half-duplex anymore?

Originally posted by jessfx

what kind of hardware only uses half-duplex anymore?

Misconfigured hardware, hence my first post. :)

as far as i know 'ifconfig' is not giving me any duplex info.

Might just be your connection, speeds to a few speed test sites are going fast as usual for me...

root@server2 [~]# wget ftp://ftp.uu.net/uumap.tar.Z
--15:03:32-- ftp://ftp.uu.net/uumap.tar.Z
=> `uumap.tar.Z.3'
Resolving ftp.uu.net... done.
Connecting to ftp.uu.net[192.48.96.9]:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD not needed.
==> PORT ... done. ==> RETR uumap.tar.Z ... done.
Length: 8,520,221 (unauthoritative)

100%[=================================================================================>] 8,520,221 1.84M/s ETA 00:00

15:03:37 (1.84 MB/s) - `uumap.tar.Z.3' saved [8520221]

Do it on your server, and if you don't get similar results, have Nocster check out your NIC card.

- Matt

I think first you should consult Nocster on what the problem is.
If you are a long client, may be your server has been rate limited :P

Originally posted by VapoRub
I think first you should consult Nocster on what the problem is.
If you are a long client, may be your server has been rate limited :P

well i am paying for an uncapped 100mbps connection so I don't think i am rate limited.

ok forgive my newbie status here but what's a long client?

Originally posted by mainarea
Do it on your server, and if you don't get similar results, have Nocster check out your NIC card.

i have submitted a ticket already (waiting for reply).

i am getting similar results on the speed. i guess this implies that this is not a problem with the NIC card and that Nocster has a fat pipe to UUNet

i'm still just wondering if anyone who is a nocster client is experiencing slow connections :)

Nocster doesnt have a "fat pipe to UUNET"

jessfx - Nocster doesn't have any direct connection to UUNet, and hasn't for about a year :D. (Their route to UUNet goes over their Cogent line) Please post a traceroute to your server, so that people can see if there's an issue with the route that you're taking.

-Josh

my apologies. what i meant was that i was getting decent speeds to the uunet ftp site, not necessarily that they had a direct connection.

but at the end of the day it doesn't matter if i can ftp a file from uunet at fast speeds ... it matters how fast i can connect to the server and how fast other people can connect to the server

if all i can do with the server is ftp a file from uunet quickly then that is almost useless

i am getting horrible speeds from nocster that i have not been getting from other datacenters and this is worrying

I get 900K-1MB/s (7.2-8Mbps) to my server in TX from Nocster. What IP are you trying to transfer data from, to Nocster? Speeds look fine to me from a server in Texas, UUNet, AOL, and a server in California - I don't think this is necessarily a Nocster problem.

- Matt

Originally posted by mainarea
I get 900K-1MB/s (7.2-8Mbps) to my server in TX from Nocster. What IP are you trying to transfer data from, to Nocster? Speeds look fine to me from a server in Texas, UUNet, AOL, and a server in California - I don't think this is necessarily a Nocster problem.

- Matt

thanks for your input. from datacenters in texas (ev1 and theplanet) direct to me i get much faster speeds than from nocster (east coast) direct to me.

from those servers to nocster i am not getting anything i would call normal or fast (~400kbps / 50KBps). this may not be a problem with nocster network wide but perhaps a problem with my subnet or a particular issue they are having with a router or something.

What is your IP, and what kind of connection are you on? I max out my 3Mbps cable line when downloading from Nocster, and I'll try to see if I can test the speeds tomorrow from a local T3 line (:) mmm.... T3 speed... :D)

- Matt

mainarea i sent you a PM ... are you accepting them?

Yes - I'll try to help you with your problem.

- Matt

update from pm:

mainarea - my connection to your server is also very slow (about the same as when i connect to my server)

also the connection from my ev1 server to your nocster/burst server is about the same as to my nocster/burst server

this seems to indicate that this speed issue is not just confined to my nocster/burst server

Hey , I know this *was* not just an issue with him because me and my friend had the same problems and created tickets. It seemed to be yet another network issue. But its been fixed now but, for the last 3 days there has been major packet loss... http://forums.burst.net/showthread.php?threadid=2178 and I am still waiting for this to be fixed...

Originally posted by Spider210
Hey , I know this *was* not just an issue with him because me and my friend had the same problems and created tickets. It seemed to be yet another network issue. But its been fixed now but, for the last 3 days there has been major packet loss... http://forums.burst.net/showthread.php?threadid=2178 and I am still waiting for this to be fixed...

how slow are your transfers may i ask?

i read that before i posted here but i didn't think it could be the only cause (which is why i asked if anyone was experiencing slowdowns as well). also if this problem has been fixed then it still doesn't explain why my transfers from different locations to my server and mainarea's server was so slow.

The packetloss is not the cause of this network issue that jessfx is seeing, and it has not affected speeds at all.

- Matt

update:

the network is once again insufferably slow

PLEASE post a traceroute. Nocster is NOT having any issues right now, and I can download files from my server at normal speeds from 3 locations in the US.

-Josh

Josh

Is it ok if i send you a PM with the traceroute?

-Jessie

Yes, you can PM me with the traceroute.

5 9 ms 12 ms 11 ms leg-208-30-204-161-RIA.sprinthome.com [208.30.20
4.161]
6 24 ms 34 ms 24 ms 144.232.13.145
7 23 ms 20 ms 29 ms sl-bb24-nyc-10-0.sprintlink.net [144.232.13.181]

8 21 ms 37 ms 20 ms sl-bb21-nyc-6-0.sprintlink.net [144.232.13.186]

9 28 ms 25 ms 25 ms p16-0-1-2.r20.nycmny01.us.bb.verio.net [129.250.
9.173]
10 33 ms 40 ms 24 ms p64-0-0-0.r21.nycmny01.us.bb.verio.net [129.250.
2.33]
11 35 ms 27 ms 24 ms p16-4-0-0.r01.nwrknj01.us.bb.verio.net [129.250.
5.12]
12 23 ms 26 ms 25 ms p4-0-1.a03.phlapa01.us.ra.verio.net [129.250.16.
121]
13 26 ms 27 ms 27 ms fa-0-0.a05.phlapa01.us.ra.verio.net [129.250.116
.197]
14 138 ms 376 ms 269 ms ge-1-2.a01.phlapa04.us.ra.verio.net [129.250.116
.213]
15 25 ms 27 ms 23 ms ge-1-2.a01.phlapa04.us.ce.verio.net [130.94.0.16
6]
16 32 ms 33 ms 45 ms ge-7-0-ctsi.rtr0.scra1.HOSTNOC.net [66.197.191.4
5]
17 31 ms 28 ms 33 ms 66.197.191.82
18 40 ms 31 ms 31 ms 64.191.81.149


There's a latency spike on hop 14, but nothing that has been affecting me. (I should also note I have other transfers running on the connection...)