Sometimes www.perlmonks.org takes ages to respond when I click (when already logged in). I don't know whether this is due to
1. Spyware on my MacOsX machine OR
2. My ISP doing me down on the bytes/second I have paid for OR
3. The server at perlmonks being overloaded OR
4. Something else.

I used Supersearch to try to find anything on this, but drew a blank.

I'm particularly interested in Perlish ways of investigating point 3 but help with the other points, and/or /.*x/ methods, would also be helpful.

Thanks a lot

dbae

Replies are listed 'Best First'.
Re: Response time from perlmonks
by xdg (Monsignor) on Aug 18, 2005 at 10:31 UTC

    I turned off a lot of the nodelets and that seemed to help a little bit. I suspect it's load related as I've noticed it seems more sluggish during lunchtime on the US east coast.

    -xdg

    Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

[reply]
      I'm not sure what is meant by turning off a nodelet. I only have a maximum of one nodelet showing in my browser (Firefox) at any one time, so there doesn't seem to be anything to turn off. Can highly XPd monks display many nodelets at one time?

      I think I should perhaps have posted this to SoPW, as I really wanted an answer as to whether/how it is possible to find out directly how long the server is taking---as I explain in my post, there are so many other factors that could be affecting the response. I posted here because it "concerns the perlmonks site", but that was probably an inXPd way to proceed. The same code could then perhaps be used to interrogate non-monkish websites that are running slowly.

      Thanks

      dbae

[reply]

        In your "user settings" (see your user page), you can enable or disable various nodelets. See What are Nodelets?. Many of them apparently fetch content and that can slow things down. (Read that somewhere but can't remember where.)

        -xdg

        Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

[reply]
Re: Response time from perlmonks
by demerphq (Chancellor) on Aug 18, 2005 at 15:15 UTC

    We fight a steady ongoing war against server slowdown. As the site scales up we sometimes identify new hot spots in the code and try to resolve them. At times there are definately load issues on the site. One thing that you may want to try is to switch to the .com or .net domains as often they are lower load.

    BTW, tye has been doing a lot of work lately on improving caching and other related speed up work, so you can expect sometime in the future that he rolls it all out and hopefully shave some seconds off peak-time fetches.

    ---
    $world=~s/war/peace/g

[reply]

      Hmm. I didn't even realize that .com/.net resolved to a different IP. Would it be possible to round-robin the DNS for all three suffixes between the two hosts and automate the load sharing?

      -xdg

      Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

[reply]

        That's how it already is.

        - tye        

[reply]
Re: Response time from perlmonks
by sparkyichi (Deacon) on Aug 18, 2005 at 14:34 UTC
    I just wanted to point out PerlMonks has gotten much better over the years as far as access speed is concerned. However, please remember to visit the Offering Plate if you are able to do so.

    End Shameless Beg for Donations

    Sparky
    FMTEYEWTK
[reply]

Back to Perl Monks Discussion