Download speeds - need a few 2nd opinions :)

yes it is very possible to do only windows http, but it would take a lot of time and rules, and I just can’t see them doing this! I am still checking it a bit.

CCA yes I meant consistently the same level of speeds around the world.

Here is another test, since you mentioned one on jodohost.com also moving slow. I have a server I am testing that is based on windows as well :wink: just a bit different I will let a few of you take guesses if you want.

But here is a copy of the jodohost.com site over on it that I am working on fixing a few issues before making it live, how is it working for you?

http://64.187.104.2/downloads/user.zip

double the speed, about 66kb/s…which is about normal for my connection to the us.

Woah, major difference, I got over 100KB/sec on that one! Can you put up a bigger file, say 5MB so I can see what it really gets up to?

a) What is different about that server?
b) Can I have one? :slight_smile:

[ed] I see what you mean about the hotlinking now.. :doh:

[ed2] So Stephen, if I can now get fast HTTP from that new Win machine, I guess that means your other Win boxes have some configuration issue within your network, whatever it may be… because it’s evident now that nothing external is throttling it. :eyebrows:

Well sadly, this windows server deoesn’t look like it will ever make it into hpshere :frowning:

No there is no distinct change to be applied, this is a very different version of windows :smiley: built upon a new code base in many ways, including the tcp layer.
It is IIS7 on windows 2008

I will try to get a larger file up there but I have some business meetings here in the next few hours and need to take care of them first for today.

No problem. Interesting though… do you think it’s HSphere that’s somehow throttling http speed?

I did some searching on the issue and came across a recent post on WHT about d/l speed being slow from Jodo.. that’s a shame, but sounds like we may be on the verge of pinpointing the problem. We have to work out if HSphere is the culprit or not - that was the main difference in the above test, yeah? Is it possible to plug that Win2008 machine into the same switch as one of the slow Win servers so we can rule out any network issues there? If it’s still fast, then it points suspiciously to HSphere..

It isn’t a switch issue, cl2win3 and win27 are the same switch :smiley:

Is cl2win3 is also a fast downloder? That would be important, as it’s the only HSphere Win machine that’s fast. All the others I tested incl. Win27 were slow..

Can you put a file up on cl2win3 for me to test?

I have cluster2 win3 maxing out my measly 1.5mb verizon dsl here in TX, win7 and win14 also do it just tested from here again :smiley:

Attach win3

Just a note, cluster2 is a different network with a little different peering arrangement with providers as well, so I am really curious on this one :smiley:

win3cl2download1.jpg

Bingo! Downloaded: http://win3.g********.com/adminpak.zip at ~190KB/sec. When can I move my sites across? :slight_smile: Seriously, if that’s in production I’d like to move at least one customer across. So it’s the peering that’s the issue?

[code]Tracing route to win3.g********.com [64.71.229.15]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.254
2 15 ms 15 ms 16 ms nexthop.wa.ii.net [203.59.14.16]
3 16 ms 16 ms 16 ms gi2-4.per-qv1-bdr1.ii.net [203.215.4.32]
4 72 ms 73 ms 73 ms gi0-15-1-1.syd-ult-core1.ii.net [203.215.20.4]
5 73 ms 73 ms 73 ms 202.139.19.33
6 230 ms 231 ms 230 ms 203.208.191.157
7 236 ms 231 ms 231 ms 208.50.13.185
8 302 ms 286 ms 285 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
9 286 ms 287 ms 287 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net [64.212.16.166]
10 286 ms 286 ms 286 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]
11 287 ms 287 ms 287 ms webhosting-9.border5.mia003.pnap.net [216.52.162.66]
12 287 ms 287 ms 287 ms 64.71.225.26
13 288 ms 288 ms 288 ms 64.71.229.15

Trace complete.[/code]

dl-win3.gif

all cluster2 i on this other network. It is production and in about 10-15 days it will even be off signup, as Win4 will be in, so very near to the point of stopping signups on it.

So it has about normal levels of traffic and usage, compared to other servers. What I mean by this is that it is not a config related issue or anything.

You can’t move an account between clusters, but we plan on some changes over the coming months that will certainly increase such speeds across the board :slight_smile: More will be coming on this as we bring it live.
If you need though, you are free to do a cluster2 account and it will go here to this other network.

Ok, thanks Stephen, great to finally find out what was causing the slowness! http://d2826846.ao81.activeorg.com/smilies/cheerleader.gif :slight_smile:

Questions:

  1. When you say it’s going off signup, do you mean reseller or shared signups?

  2. If you mean reseller, does that mean I need to start a new reseller account and specify cluster 2, then all my client signups will be on cluster2, even after the 15 days are up?

  3. After signups are turned off for cluster2, what happens then? Do new signups go back onto cluster1?

No cluster1 and 2 are totally different.

I mean that win4 is coming in and win3 will not be the currently active for signup server :slight_smile: for cluster2 :smiley:

Ah ok. So win4 signup is also on Cluster 2 then? Or is there going to be a Cluster 3?

And my other q’s… to get onto this faster connected cluster, do I have to sign up for a new reseller account?

i.e. you said I can “do a cluster2 account” - what’s the process there exactly? I really need this, as soon as possible.

all new accounts go to cluster2, there won’t be a cluster3 so far as I know :slight_smile: so any new reseller signup is on cluster2.

There is a reason why peering is not the same on both networks, and it is related to an IP ownership issue that we are working out :wink:

It is also the reason for the IP reverse whois names that some people are complaining about, but ARIN is getting very strict on it and now even checking company backgrounds before issuing IPs which prevents us from making the “JD NexGen” name like we had before as a name for the whois on IPs.

Not surprising, IPv4 is becoming a little crowded. :shocked: Ok, I’m getting myself a cluster 2 then, because this one is dog slow. I was about to go set up a couple of important clients ELSEWHERE, can you believe it? :slight_smile:

Questions:

  1. Can you guys do client account moves to the new reseller account for me?

  2. When this “IP ownership issue” is resolved, are you going to revert cluster 2 back to the same peering as cluster 1? I need to know that now. No point moving across if it’s going to end up slow as mollases again. Better yet, put C1 on the same peering as C2, it’s a serious improvement!

We are working on new and improved peering arrangements for both, it won’t be going the way of cl1 on peering :slight_smile:

Good news! But you skipped Q1. :slight_smile: Can you guys do client account moves to the new reseller account for me after I set it up? Or is that too complicated, considering SQL servers, mail, etc?

I mean, if Cl1 peering was gonna be changed soonish, like in the next month or two, then I’ll stay put. But it’s shocking for my poor clients, if it’s going to be at least 3 months, I’ll do whatever I need to move over.

Can’t you weave some magic and just dump my reseller a/c + clients onto Cl2? (always hopeful) :rolleyes: Or do I have to recreate everything from scratch, including new *SQL db’s? Hope not.. :frowning:

lol.. just signed up another reseller a/c and got a phone call from Jodo! That didn’t happen last time.. first time speaking to you/them on the phone after all this time! Assuming it wasn’t a call-centre thing. Indians are so polite. :smiley:

No our phone calling is all in house, we have a very high rate of fraud signups and some are so bad we don’t even call it is so obvious, but every other person gets a phone call to verify 1. the number is good 2. the purchase is legit.

Now as for transferring, it isn’t something that can really be done easily.