• Please review our updated Terms and Rules here

Sluggish Forum Performance

Maverick1978 said:
FWIW, Chromedome45 and I were talking this past Saturday about the general sluggishness of VCF.

He's on a Comcast connection, and it's dirt-slow for him almost constantly the last several days. I'm running from a dual-pipe AT&T/Brighthouse connection, and I've noticed absolutely no slowdown for me, regardless of the time of day or night.

The only thing I can think of (and I've not researched this at all, just a hunch on my part) is the correlation to Level 3. As probably most of you know. Level 3 provides the nationwide backbone for Netflix, and they're also the major backbone supplier of Comcast's nationwide connection. Netflix gets bogged down, Comcast gets bogged down. This is why Comcast is embroiled in a lawsuit against Level 3. If Ole Juul's traces are constant in that many of us are having Level 3 as a hop on the forward/return trip to the VCF server, I'd be curious if that turns out to be the bottleneck.
Click to expand...

It's good to know that there is some verification that this is happening to others. The Giraffe Board hasn't added to the previous post that I mentioned, but I see they have quite a few threads with the subject of slow board, so it's obviously common experience with vBulletin on UrlJet.

I think deathshadow pointed out the most important thing though, and that is the unusual (unacceptable?) nature of the vBulletin code. Regardless, there are two issues in this thread. The one that I added (hijacked thread) was about the broken maintenance effort - which got fixed. It does show that something is not quite right with either vBulletin or UrlJet.

No, my traces are not constant. It went through Comcast and stayed that way for a day or so, but when I rechecked last night it had changed. I don't know offhand where Hurricane Electric fits into the scheme of things. Here is the latest route - minus my locals:

Code: 
 6  ra1ht-ge3-2-16.ok.bigpipeinc.com (64.251.64.57)  8ms  8ms  7ms
 7  rd1ht-ge3-48.ok.shawcable.net (66.163.72.174)  9ms  8ms  8ms
 8  66.163.76.82 (66.163.76.82)  25ms  22ms  22ms
 9  rc1nr-pos0-7-4-0.wp.shawcable.net (66.163.76.194)  36ms  37ms  39ms
10  66.163.78.42 (66.163.78.42)  57ms  52ms  57ms
11  10gigabitethernet4-1.core1.chi1.he.net (206.223.119.37)  63ms  52ms  61ms
12  10gigabitethernet1-1.core1.mci1.he.net (72.52.92.2)  64ms  65ms  63ms
13  10gigabitethernet2-2.core1.mci3.he.net (184.105.213.34)  65ms  70ms  62ms
14  admo-net.gigabitethernet1-14.core1.mci3.he.net (184.105.250.42)  63ms  66ms  63ms
15  server13.urljet.com (199.193.245.217)  66ms  66ms  64ms
 
Wow, that's blazingly fast compared to mine, where the total ping time is up around a full second.
Code: 
  6    29 ms    42 ms    31 ms  107.14.19.26
  7    30 ms    30 ms    31 ms  107.14.17.169
  8    67 ms    68 ms    66 ms  xe-5-3-0.edge2.Newark1.Level3.net [4.59.20.37]
  9    73 ms    71 ms    73 ms  ae-32-52.ebr2.Newark1.Level3.net [4.69.156.62]
 10    68 ms    67 ms    68 ms  ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101]
 11    76 ms    74 ms    74 ms  ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
 12    68 ms   103 ms    68 ms  ae-61-61.ebr1.Washington1.Level3.net [4.69.134.129]
 13    67 ms    67 ms    66 ms  ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
 14    74 ms    73 ms    73 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 15    72 ms    72 ms    73 ms  ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]
 16    72 ms    73 ms    74 ms  ae-92-92.ebr2.Dallas1.Level3.net [4.69.151.166]
 17   105 ms   107 ms   107 ms  ae-5-5.car1.KansasCity1.Level3.net [4.69.135.229]
 18   106 ms   107 ms   107 ms  ae-11-11.car2.KansasCity1.Level3.net [4.69.135.234]
 19   106 ms   111 ms   107 ms  ADMO.NET-WE.car2.KansasCity1.Level3.net [4.53.34.26]
 20   106 ms   107 ms   107 ms  server13.urljet.com [199.193.245.217]
That's with time warner roadrunner, pulling out the 40ms spent at ne.northeast.rr.com. The amount of time spent bouncing around Level3 is ridiculous... though my being in New England means to reach the midwest my signal either has to bounce across the atlantic and back first, or up to canada, across to vancouver and back.

But again, I get faster ping times across the ocean to Europe than I do to New York City 200 miles to the south or across to the alleged "backbone mecca" of Chicagoland... which is why "Oh it's fast enough where I am" is often 100% grade A manure unless you're in the golden zones of the midwest/southeast or pacific rim... Pretty much shtupping Canada, New England and most of Europe in the process.

See why I often got better average speeds on a tier 4 server in Vancouver, than I did with a Tier 1 hosting service out of the Chicagoland area. The teir 1 might have been blazingly fast for people across the south and midwest, but it was USELESS everywhere else on the planet.
 
Last edited:
In regards to Level 3, don't forget that they change routes according to traffic/price with their business partners... unlike Tier 1 providers, you don't get a constant/guaranteed route around the net.

FWIW, therein is the reason for the price differential between a Tier 1 provider and Tier 2/3/4 providers...
 
The only bottleneck I had here was the forum being unresponsive two days ago for only about 15 minutes. No performance issues have came up since then.
 
I've seen no issues at all over the last days from here in Norway. The forum is as snappy as ever (unlike another forum in the US which I'm also accessing). So the problem could be related to your local ISP or in-between routing.

-Tor
 
You must log in or register to reply here.
Back
Top