My first attempt at a "blog", whatever that means.
Published on September 9, 2008 By MottiKhan In Forum Issues

There was a post by Mumblefratz earlier about the forums being slow, but it has evidently been deleted.  I responded to another saying that the speed problem was fixed, but I spoke too soon.  It worked for maybe 5 minutes and went back to being incredibly slow. Not 10 or 15 seconds slow, but at least 30 seconds to load a page, most times more than 30 seconds.

The only websites I'm having problems with are forums.galciv2.com and forums.stardock.com.

In the deleted post, a tech asked for PING and TRACERT data.  I'm posting mine for forums.galciv2.com along with a PATHPING. I hope this helps.

-PING

Pinging forums.galciv2.com [209.124.63.234] with 32 bytes of data:



Reply from 209.124.63.234: bytes=32 time=91ms TTL=108

Reply from 209.124.63.234: bytes=32 time=91ms TTL=108

Reply from 209.124.63.234: bytes=32 time=91ms TTL=108

Reply from 209.124.63.234: bytes=32 time=91ms TTL=108



Ping statistics for 209.124.63.234:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 91ms, Maximum =  91ms, Average =  91ms

 

 

-TRACERT

Tracing route to forums.galciv2.com [209.124.63.234]

over a maximum of 30 hops:



  1   <10 ms   <10 ms   <10 ms  (Address Removed For Security)

  2    44 ms    26 ms    25 ms  (Address Removed For Security)

  3    41 ms    40 ms    41 ms  at-6-0-0-1711.CORE-RTR2.DFW01.verizon-gni.net [130.81.36.58]

  4    41 ms    42 ms    42 ms  so-0-0-0-0.BB-RTR2.DFW01.verizon-gni.net [130.81.20.62]

  5    39 ms    39 ms    55 ms  so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.175]

  6    39 ms    39 ms    61 ms  po1-0.core01.dfw03.atlas.cogentco.com [154.54.10.217]

  7    39 ms    39 ms    40 ms  te8-2.mpd01.dfw03.atlas.cogentco.com [154.54.5.190]

  8    40 ms    41 ms    39 ms  te3-2.mpd01.dfw01.atlas.cogentco.com [154.54.6.57]

  9    49 ms    49 ms    49 ms  te8-2.mpd01.mci01.atlas.cogentco.com [154.54.5.126]

 10   252 ms   219 ms   232 ms  te4-3.mpd01.ord01.atlas.cogentco.com [66.28.4.186]

 11    84 ms    84 ms    84 ms  gi12-0-0.core01.ord01.atlas.cogentco.com [154.54.1.97]

 12   112 ms   128 ms    95 ms  po5-0.core01.tol01.atlas.cogentco.com [154.54.5.154]

 13    91 ms    91 ms    91 ms  po5-0.core01.dtw04.atlas.cogentco.com [154.54.1.2]

 14    93 ms    93 ms    93 ms  vl3801.na31.b020673-1.dtw04.atlas.cogentco.com [38.112.37.86]

 15    91 ms    92 ms    91 ms  38.104.38.10

 16    91 ms    92 ms    91 ms  216.234.104.162

 17    92 ms    92 ms    93 ms  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]

 18    92 ms    92 ms    92 ms  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]



Trace complete.

 

 

-PATHPING



Tracing route to forums.galciv2.com [209.124.63.234]

over a maximum of 30 hops:

  0  (Address Removed For Security)

  1  (Address Removed For Security)

  2  (Address Removed For Security)

  3  at-6-0-0-1711.CORE-RTR2.DFW01.verizon-gni.net [130.81.36.58]

  4  so-0-0-0-0.BB-RTR2.DFW01.verizon-gni.net [130.81.20.62]

  5  so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.175]

  6  po1-0.core01.dfw03.atlas.cogentco.com [154.54.10.217]

  7  te8-2.mpd01.dfw03.atlas.cogentco.com [154.54.5.190]

  8  te3-2.mpd01.dfw01.atlas.cogentco.com [154.54.6.57]

  9  te8-2.mpd01.mci01.atlas.cogentco.com [154.54.5.126]

 10  te4-3.mpd01.ord01.atlas.cogentco.com [66.28.4.186]

 11  gi12-0-0.core01.ord01.atlas.cogentco.com [154.54.1.97]

 12  po5-0.core01.tol01.atlas.cogentco.com [154.54.5.154]

 13  po5-0.core01.dtw04.atlas.cogentco.com [154.54.1.2]

 14  vl3801.na31.b020673-1.dtw04.atlas.cogentco.com [38.112.37.86]

 15  38.104.38.10

 16  216.234.104.162

 17  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]

 18  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]



Computing statistics for 450 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           (Address Removed For Security)

                                0/ 100 =  0%   |

  1    0ms     0/ 100 =  0%     0/ 100 =  0%  (Address Removed For Security)

                                0/ 100 =  0%   |

  2   41ms     0/ 100 =  0%     0/ 100 =  0%  (Address Removed For Security)

                                0/ 100 =  0%   |

  3   55ms     0/ 100 =  0%     0/ 100 =  0%  at-6-0-0-1711.CORE-RTR2.DFW01.verizon-gni.net [130.81.36.58]

                                0/ 100 =  0%   |

  4   52ms     0/ 100 =  0%     0/ 100 =  0%  so-0-0-0-0.BB-RTR2.DFW01.verizon-gni.net [130.81.20.62]

                                0/ 100 =  0%   |

  5   53ms     0/ 100 =  0%     0/ 100 =  0%  so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.175]

                                0/ 100 =  0%   |

  6   51ms     0/ 100 =  0%     0/ 100 =  0%  po1-0.core01.dfw03.atlas.cogentco.com [154.54.10.217]

                                0/ 100 =  0%   |

  7   53ms     0/ 100 =  0%     0/ 100 =  0%  te8-2.mpd01.dfw03.atlas.cogentco.com [154.54.5.190]

                                0/ 100 =  0%   |

  8   57ms     0/ 100 =  0%     0/ 100 =  0%  te3-2.mpd01.dfw01.atlas.cogentco.com [154.54.6.57]

                                0/ 100 =  0%   |

  9   72ms     0/ 100 =  0%     0/ 100 =  0%  te8-2.mpd01.mci01.atlas.cogentco.com [154.54.5.126]

                                0/ 100 =  0%   |

 10  104ms     0/ 100 =  0%     0/ 100 =  0%  te4-3.mpd01.ord01.atlas.cogentco.com [66.28.4.186]

                                0/ 100 =  0%   |

 11   92ms     0/ 100 =  0%     0/ 100 =  0%  gi12-0-0.core01.ord01.atlas.cogentco.com [154.54.1.97]

                                0/ 100 =  0%   |

 12   98ms     0/ 100 =  0%     0/ 100 =  0%  po5-0.core01.tol01.atlas.cogentco.com [154.54.5.154]

                                0/ 100 =  0%   |

 13  103ms     0/ 100 =  0%     0/ 100 =  0%  po5-0.core01.dtw04.atlas.cogentco.com [154.54.1.2]

                                0/ 100 =  0%   |

 14  104ms     0/ 100 =  0%     0/ 100 =  0%  vl3801.na31.b020673-1.dtw04.atlas.cogentco.com [38.112.37.86]

                                0/ 100 =  0%   |

 15  113ms     1/ 100 =  1%     1/ 100 =  1%  38.104.38.10

                                0/ 100 =  0%   |

 16  104ms     1/ 100 =  1%     1/ 100 =  1%  216.234.104.162

                                0/ 100 =  0%   |

 17  103ms     0/ 100 =  0%     0/ 100 =  0%  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]

                                8/ 100 =  8%   |

 18   97ms     8/ 100 =  8%     0/ 100 =  0%  234.63.124.209.sfldmi01.utropicmedia.net [209.124.63.234]



Trace complete.

 


Comments (Page 2)
3 Pages1 2 3 
on Sep 11, 2008

For those of you using Firefox, I recommend the extended statusbar plugin, it will tell you how long and at what speed it takes to load a page.

on Sep 11, 2008

Okay, I'm impressed by all of the routing data, interesting to know you can do this, are we using a specific program to accomplish these traces?

 

 

on Sep 11, 2008

I just want to iterate that for me at least (and I'm fairly sure there have been a few others that have made similar comments) that this issue appeared pretty much instantaneously. Everything had been working perfectly normally and then suddenly in the Sunday to Monday timeframe (9/7 - 9/8) every page access slowed down to the 30-45 second range.

Clearly something changed but that probably doesn't really limit the scope. It could be an obscure hardware failure or it could even be related to Forum Update v1.6.3174.27495 which *I think* occured within this timeframe or a multitude of other things.

I don't know how feasible this is but has any thought been given to "rolling back" the recent forum changes merely as a test?

on Sep 11, 2008

Okay, I'm impressed by all of the routing data, interesting to know you can do this, are we using a specific program to accomplish these traces?

They're standard DOS commands.  Just open a DOS window and type PING, TRACERT or PATHPING a space and the destination (forums.stardock.com for example).  If you want to capture it in a text file, add another space and type >text.txt or whatever you care to name the file.  It'll show up in the path that you used to issue the command (C:\Windows\Profiles\Me for example.)

 

on Sep 11, 2008

MottiKhan, thanks, could be entertaining.

on Sep 11, 2008

Seems fixed. 

Last three pages loaded is a handful of seconds. Dramatic improvement. Anyone else noticing it or am I just getting lucky?

on Sep 11, 2008

Just getting lucky,

I repeated my traces,

I'm getting the exact same results as I posted above!

on Sep 11, 2008

Just getting lucky
Hmm ... That's too bad I was hoping it was fixed. However I continue to see page load (and render) times on the order of 2 to 3 seconds when for the last 3 days it's been a very dependable 30 to 45 seconds.

My TRACERT data is virtually identical compared to when I was running slow.

C:\Documents and Settings\Administrator>tracert forums.galciv2.com

Tracing route to forums.galciv2.com [209.124.63.234]
over a maximum of 30 hops:

  1    <1 ms     2 ms    <1 ms  dslmodem.domain [192.168.1.1]
  2    33 ms    33 ms    32 ms  
  3    35 ms    35 ms    34 ms  so-0-2-3-0.CORE-RTR1.BOS.verizon-gni.net [130.81.7.193]
  4    37 ms    36 ms    37 ms  so-0-2-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.20.84]
  5    35 ms    37 ms    36 ms  130.81.17.61
  6    42 ms    48 ms    43 ms  130.81.17.24
  7    41 ms    41 ms    57 ms  so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131]
  8    42 ms    41 ms    39 ms  po2-0.core01.jfk05.atlas.cogentco.com [154.54.11.45]
  9    41 ms    42 ms    41 ms  te4-1.mpd01.jfk05.atlas.cogentco.com [154.54.1.153]
 10    42 ms    41 ms    40 ms  vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
 11    47 ms    45 ms    47 ms  te2-4.ccr02.bos01.atlas.cogentco.com [154.54.6.9]
 12    48 ms    46 ms    44 ms  gi11-0-0.core01.bos01.atlas.cogentco.com [154.54.5.21]
 13    64 ms    63 ms    65 ms  po6-0.core01.cle01.atlas.cogentco.com [66.28.4.158]
 14    65 ms    66 ms    65 ms  po6-0.core01.tol01.atlas.cogentco.com [66.28.4.222]
 15    66 ms    65 ms    66 ms  po6-0.core01.dtw04.atlas.cogentco.com [154.54.25.110]
 16    65 ms    66 ms    65 ms  vl3501.na31.b020673-1.dtw04.atlas.cogentco.com [38.112.37.82]
 17    64 ms    71 ms    78 ms  38.104.38.10
 18    66 ms    66 ms    65 ms  216.234.104.162
 19    68 ms    67 ms    69 ms  forums.galciv2.com [209.124.63.234]
 20    68 ms    65 ms    67 ms  forums.galciv2.com [209.124.63.234]

Trace complete.

I think this low level path stuff is a dead end. I see no difference between this and my previous posting yet before I was running 30-45 seconds per page now its 2-3 seconds.

on Sep 12, 2008

Mumblefratz
Seems fixed. 

Last three pages loaded is a handful of seconds. Dramatic improvement. Anyone else noticing it or am I just getting lucky?

I posted yesterday saying that it seemed to be fixed too after the forums sped up for at least 30 minutes.  I didn't want to claim a false victory a second time.  I deleted the post when, as if on cue, the forums went from 1.88 second renders to 30+ second renders right after my post.  It took over 10 minutes to delete the post.

It's back to being fast again for the time being.

on Sep 12, 2008

Still fast for me consistently for the last 14 hours but I also am not declaring victory. Clearly while my access was fast others were slow. This just indicates the variablity of the problem. It also to some extent indicates that this is *not* a client side problem. I've gone from working fine to extreme slowdown and back again without a single hardware or software change to my PC. How can that indicate a problem with my PC, or anyone else's PC for that matter?

on Sep 12, 2008

It could indicate stability problems with your ISP. I also experience minor variations in the render time, but on much smaller scale, ranging from 0.5 seconds to about 2-3 seconds. Negligible, really.

 

On the other hand, I have serious problems with Impulse sometimes. Download rates vary from a 350+ kb/s to below 10 kb/s. Extremely annoying when downloading complete games or large patches.

on Sep 12, 2008

pndrev, please stay on topic. We tend to moderate off topic replies, or tangents in replies in the Forum Issues forum. If you have issues with another product or Forum function, please create a new post.

on Sep 12, 2008

It's been working fine for me since late yesterday.  A little slower when logged in than when viewing as a guest.  This page loaded in about 2 seconds as a guest and 5.964 seconds logged in.  Firefox also shows about 2 seconds as a guest, but the time went up to 29.513 seconds when logged in. 

In reality though, the page displayed fine within 3 or 4 seconds when logged in.  I'm not sure why the Stardock and Firefox timers show longer times.

Is anyone still having speed problems?  If not, this can probably be closed as resolved.

on Sep 12, 2008

Motti asked if this could still be a problem with HIS setup as opposed to YOURS. So I answer with a simple observation that an otherwise stable lines sometimes has difficulties with your servers. This is absolutely on-topic, as it may help to find the issue on his side.

I concur, and thanks for your reply, pndrev.  All seems ok now.  Something has obviously taken place, but I'm not sure what it might have been.

The number of active users indicating as approaching 700 is a good sign that all is well.  It was in the single and low two digits during the slowdown.

 

on Sep 12, 2008

All, this post has shot into a tangent following a discussion of connections to all Stardock servers/services. The intent of this post was to showcase connection problems with the forums, specifically (as indicated by the Title). While I'm not going to (further) moderate out any of the replies made before this one, any subsequent replies **not involving connections to the forums** (ie. some forum address; for example https://forums.wincustomize.com or forums.galciv2.com) will be moderated.

If any of you would like to start or continue a discussion of connectivity to a variety of servers/addresses, please do so in a new post. The 'Forum Issues' forum and posts within it are for diagnosing, debugging and resolving forum issues. If any of you would like to review the moderation policy for the Forum Issues forum/category, we have them stickied here > Forum Issues Moderation Policy

 

3 Pages1 2 3