in reply to Re^7: Perlmonks site has become far too slow
in thread Perlmonks site has become far too slow

We are using only one webserver, behind a single IP address.

  • Comment on Re^8: Perlmonks site has become far too slow

Replies are listed 'Best First'.
Re^9: Perlmonks site has become far too slow
by Discipulus (Canon) on Sep 01, 2025 at 12:08 UTC
    Hello Corion,

    > ..a single IP address..

    which one? https://www.whatsmydns.net/#A/perlmonks.org gives the 66.39.54.27

    but both still respond to my pm-monitor.pl

    perlmonks.org @ https://66.39.54.27/index.pl? 200 OK 21.6182 + Kb (22137 bytes) in 9.123193 seconds 2.3696 Kb/s perlmonks.org @ https://216.92.34.251/index.pl? 200 OK 21.6182 + Kb (22137 bytes) in 0.974809 seconds 22.1768 Kb/s

    As side note (but this might be error on my part) when I connect with the browser to the above IPs I get the certificate for css.perlmonks.org and the same from chrome: a certificate named css.perlmonks.org and no Subject nor CNs.

    Similarly from commandline:

    openssl s_client -showcerts -connect perlmonks.org:443 CONNECTED(00000264) depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Ne +twork, CN = USERTrust RSA Certification Authority verify error:num=20:unable to get local issuer certificate --- Certificate chain 0 s: <------ weird + to be empty i:/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USER +Trust RSA Domain Validation Secure Server CA ...

    L*

    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
      I'd guess it's 66, as 216 is blazing fast.

      Update: Not fast anymore. Maybe I was just lucky.

      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
Re^9: Perlmonks site has become far too slow
by LanX (Saint) on Sep 01, 2025 at 10:09 UTC
    OK strange, did I totally misremember this or did it change recently?

    I seem to remember having discussions about 2 servers having different certificates.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    see Wikisyntax for the Monastery

      It has changed recently for easier log analysis related to the bot attacks/scraping raids.
      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
        I'm ignorant about the complexity of those rules but I would consider balancing/redirecting all anonymous users to one exclusive server, maybe except for the login page.

        Like this logged in users and especially admins could work and improve the site.

        And the bot logs would be available on the other box.

        We also need a dev/test server where we can patch the core Everything:: modules, probably a second installation on the less busy hardware could do, accessible under a dedicated sub domain. Cloning the modules and libraries should do to get this running.

        High performance caching is certainly feasible, but we need to implement the triggers to disable a dependent cached page on update events. And I think we need better benchmarking than just server logs to evaluate the best strategies.

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        see Wikisyntax for the Monastery