in reply to Disappointed with perlmonks' speed (discussion)

I have a feeling it's something upstream of PM. I've seen the same problems from two different access points with PM, but the symptoms make little sense for it to be a problem with CPU cycles on the local hardware. Instead, I think that a few hops upstream may be flaky, as it has more of a feel to dropped packets than it does to overloading a server.

With the ads removed, that would help the response time (presume the ads were on the same network segment but different server), but wouldn't completely remove it.

And the lost packets are not the same for everyone; I've watched CB chatter go by, and when one of the temporary speed slowdowns hit and disappate, the amount of CB chatter feels like there's been a lot more going on while I've missed it. (Also, seeing jcwren's Robomonk in action, there's been points where after Robomonk resees the site that a large influx of messages appear).

So unless I'm mistaken, I doubt there's little that can be done to fix it at vroom's end, even if more money was through at it. It's probably not even the ISP, most likely it's the next level up. But I haven't sat there with traceroutes or similar tools to isolate it as such.

Dr. Michael K. Neylon - || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important

  • Comment on Re: Disappointed with perlmonks' speed (discussion)

Replies are listed 'Best First'.
Re: Re: Disappointed with perlmonks' speed (discussion)
by kwoff (Friar) on Dec 18, 2001 at 23:08 UTC
    You're probably right, however one thing that I've noticed is that the big delay usually comes when I log in. After that it's generally useable. I often have to Stop the page during login after it spins for a minute or two, and hit the login button again. Sometimes when I then attempt to login again, it will immediately log in, but then other times it will take several attempts (maybe 5 minutes total) to get in.

    Here is a traceroute taken when I had trouble logging in (seems fine, no hangups):

    $ /usr/sbin/traceroute traceroute to (, 30 hops max, 38 byte pack +ets 1 ( 0.545 ms 0.465 ms 0.436 ms 2 ( 4.841 ms 2.600 ms 2.307 ms 3 ( 24.117 ms + 3.163 ms 5.019 ms 4 ( 3.088 ms 16.287 m +s 30.606 ms 5 ( 3.203 ms + 3.096 ms 11.059 ms 6 ( 3.256 ms + 3.082 ms 3.299 ms 7 ( 3.554 ms 3.477 ms 3. +539 ms 8 ( 3.538 ms 3.404 ms 3. +413 ms 9 ( 8.633 ms 8.595 ms 8.6 +31 ms 10 ( 8.912 ms 16.037 ms 9 +.603 ms 11 ( 89.949 ms 70.057 ms +70.201 ms 12 ( 71.379 ms 71.413 ms +71.394 ms 13 ( 115.884 ms 74.740 ms + 78.527 ms 14 ( 76.103 ms 76.653 ms 76.478 ms 15 ( 78.098 ms 78.423 ms 77.512 ms 16 ( 74.470 ms 93.624 ms 75.2 +80 ms

Re: Re: Disappointed with perlmonks' speed (discussion)
by vladb (Vicar) on Dec 18, 2001 at 07:02 UTC
    On my side, I rarely experience large page load delays. I browser permonks both at work (actually the company -- TELUS --I work for sells ADSL to local population) and from home, where I'm hooked up to a 1.5 Mbps ADSL line (provided by my company).

    Certainly, buying new hardware would never hurt. I'm wondering wherethere there's a mentioning on this site which server it runs on? In any event, more $$ will always equate to better hardware and greater performance... (I'm considering to put some of my paycheque on the offering plate to aide the process).