I know I said recently, several times, that PerlMonks was easily accessible after several attempts to fix it, and many honest thank yous to Corion and everyone involved. But it seems to me that as it is now, it has degraded since then. OTOH it is much much better than when the problem peaked (and my current post had no timeout unlike other recent posts). But still it times-out quite often. Perhaps it is what I said before that if indeed the problem is caused by (decentralised) bots then they will take all available space if it is given to them by these improvements. So perhaps this is what we see, bots upping up the tempo because they found extra harvesting-bandwidth which PerlMonks itself has given them. If true, then perhaps the route of hacking the content-delivery method of the site can become soon a dead-end.

I also mentioned that PerlMonks could do with a quality-of-service monitor, as simple as recording access time of some few random nodes every few minutes. In order to assess various solutions, the problem must be quantified. This is paramount and, talking from the comfort of my keyboard, sounds easy. I think some fellow Monks here were already keeping such a record. Well, let's install this internally ASAP. EDIT: thanks to hippo I have learned that there is such QoS monitor already running, see Re^2: Still excessively slow, and graphically here https://www.perlconsultancy.com/perlmonkserrors.shtml

One added side-effect or THE main-effect is this: Searching on search-engines for something Perl-related often matches results from PerlMonks and at the very top. Which is great! Alas, I, subconsciously, avoid them or if I click on them, it is often that I have my problem solved before they open in my browser, OK exaggerating :). The gist is that the site also looses the status it had as "finding *existing* answers" and the vibe on the 'net is basically :(((( because we now have to access the &$^$&#@& Overflow which is steadily goose-stepping into fascism-land and has really become an uncomfortable experience for free-spirited minds. I wish I could avoid it, at least for Perl.

I wonder what happens when sites infested by these decentralised bots, i.e. those emanating from random, personal devices and IPs etc., are hosting advertisements. Do these sites see an exponential increase in ad-related revenues because of the bot-attacks? If the access-related problems we see with PerlMonks can be solved with money, then perhaps do consider joining the dark site? !Heresis! I know.

Apropos heresis (OT), I propose a new XP level: Heretic. It can be even on top of Pope.

thanks for all the fish, bw, bliako

In reply to Re: Still excessively slow by bliako
in thread Still excessively slow by GrandFather

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.