in reply to Re^6: super slow
in thread super slow

pm server stats is now being updated. It shows the stats for the last 7 days on a per-hour basis in a table. Sorry, but no fancy graphs. If that's something people really want, i'm sure i can come up with an ASCII-Art version via GnuPlot.

The external website will take a bit longer, but i wanted to put at least something online as soon as possible.

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
Also check out my sisters artwork and my weekly webcomics

Replies are listed 'Best First'.
Re^8: super slow
by choroba (Cardinal) on Aug 22, 2024 at 14:19 UTC
    ++ 
    set xdata time
set timefmt '%Y-%m-%d %H:%M:%S'
set term dumb
plot 'data' u 1:4 w lines title "min", \
         "" u 1:5 w lines title "avg", \
         "" u 1:6 w lines title "max"

    [download]
      14 +----------------------------------------------------------------
+-----+   
     |    +     +    +     +    +    +     +    +    +     +    +     
++    |   
     |                                                         min ***
+**** |   
  12 |-+        $                                              avg ###
+####-|   
     |          $                                              max $$$
+$$$$ |   
     |          $                                                     
+     |   
  10 |-+       $$                                                     
+   +-|   
     |         $$                                                     
+     |   
     |         $$                        $                            
+     |   
   8 |-+       $$                        $                            
+   +-|   
     |         $ $                       $$          $  $             
+     |   
   6 |-+     $ $ $             $        $ $ $     $$ $$ $$  $         
+   +-|   
     |       $$  $            $$        $ $ $$   $  $ $ $ $ $$        
+     |   
     |      $ $  $            $$        $  $ $  $   $  $   $ $        
+     |   
   4 |-+    $ $  $         $$$  $       $  $  $$       $      $       
+   +-|   
     |   $ $     $$       $     $$     $                       $ $$   
+$$   |   
     |   $$      $$$     $      $ $$   $                       $$  $ $
+     |   
   2 |-+$        $ $     $          $ $                            $ $
+   +-|   
     |              $   $            $                              $ 
+     |   
     |  #############$$$##############################################
+##   |   
   0 +----------------------------------------------------------------
+-----+   
   08/2008/20 08/2008/21 08/2108/2108/21 08/2108/2108/22 08/2208/22 08
+/2208/22

    [download]

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
[reply]
[d/l]
[select]
Re^8: super slow
by pryrt (Abbot) on Aug 22, 2024 at 17:35 UTC

    A little over an hour ago, I had a connection-refused, so since I had just grabbed the monitor that Discipulus mentioned earlier, I started running it:

    > pm_ip_monitor.pl -c 20 -s 60
Thu Aug 22 09:03:49 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 3.704645 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 2.420785 seconds (timeout 15 s
+econds)
--------------------------------------------------------------------
Thu Aug 22 09:04:55 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 2.406652 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 2.42126 seconds (timeout 15 se
+conds)
--------------------------------------------------------------------
Thu Aug 22 09:06:00 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 2.405922 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 2.422154 seconds (timeout 15 s
+econds)
--------------------------------------------------------------------
Thu Aug 22 09:07:05 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 2.421456 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 3.828308 seconds (timeout 15 s
+econds)
--------------------------------------------------------------------
Thu Aug 22 09:08:11 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 2.428386 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 2.407986 seconds (timeout 15 s
+econds)
--------------------------------------------------------------------
Thu Aug 22 09:09:16 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           500 Can't conn
+ect to 66.39.54.27:443 (No connection could be made because the targe
+t machine actively refused it.) took 2.412528 seconds (timeout 15 sec
+onds)
perlmonks.org @ https://216.92.34.251/index.pl?         500 Can't conn
+ect to 216.92.34.251:443 (No connection could be made because the tar
+get machine actively refused it.) took 2.454082 seconds (timeout 15 s
+econds)
--------------------------------------------------------------------
Thu Aug 22 09:10:21 2024 checking perlmonks.org at 66.39.54.27 216.92.
+34.251
--------------------------------------------------------------------
perlmonks.org @ https://66.39.54.27/index.pl?           200 OK 27.8066
+ Kb (28474 bytes) in 0.852321 seconds 32.6246 Kb/s
perlmonks.org @ https://216.92.34.251/index.pl?         200 OK 27.8066
+ Kb (28474 bytes) in 0.382289 seconds 72.7372 Kb/s
--

    [download]

    (Times at UTC-0700, so my it means the outage I saw was from 16:03 (or earlier) to 16:09 UTC.)

    When I was getting a response again, I checked pm server stats, and it didn't list any problems. I waited until after 17:00 UTC, in case it was behind in updating the page, but even at 17:25, it said the 16:00 UTC hour had no issues. Since the monitor script was actively getting 500 errors, not just timing out, it seems to me that they might be checking two different things. Well, maybe it is a routing difference; but previously, when I've had the connection-refused, I get it whether through my wifi or through my phone network, and often through an external is-it-down site. Unfortunately, this time, I didn't think to confirm with external route whether it was more generally down.

    And it is interesting that most of the full hours have had 585-615 access counts, whereas the 16:00 hour only had 528 -- which is about 5/6 of the normal, which would correspond to about 10 minutes in the hour without any accesses, which matches with my ~10min of connection-refused. cavac, are you sure it's properly logging when an error occurs? Or maybe it's only specific errors that yours logs, and the error I was seeing isn't one of them?

[reply]
[d/l]

      I'm using WWW::Mechanize and checking for success(). Which should mean a non-error HTTP status code, if memory serves correctly. I have to dig deeper into this, there are most likely error conditions i don't check for. I have to simulate a few types of network errors to see how WWW::Mechanize handles these. (*)

      My stuff is still a bit alpha. Basically, i use a couple of half-hour lunch breaks this week to plonk in some extra logging into my existing chatterbot codebase, write a function to run a SELECT statement for the statistics and use existing code to update a Node on PM.

      Today i was also playing around with the code and updating the database and stuff. Plus doing a linux update, which took the whole thing offline for a few minutes. I'm not exactly sure how long chatterbot was offline today or exactly when (Lunchbreaks don't always happen at noon for me, it's more like a "when i'm hungry and i can spare the time" thing).

      (*) Most of my day-to-day dev work is web server development. Strangely enough, i hardly ever implement client code.

      PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
      Also check out my sisters artwork and my weekly webcomics
[reply]
Re^8: super slow
by Discipulus (Canon) on Aug 29, 2024 at 10:48 UTC
    Hello dear chatterbot creator,

    can you put all links belonging to chatterbot on its homenode like pm server stats and so on?

    Just because I never remember where they are. Or maybe crosslink them from cb stats, last hour of cb?

    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.
[reply]
[d/l]
[reply]
        unlock that account

        Done. I am investigating a better solution.

[reply]
        I liked ++ambrus's suggestion in the CB -- once the gods re-enable chatterbot, start posting chatterbot-related announcements from that account rather than from the cavac account, so that the bot can earn some well-deserved XP.

        Also, if the gods changed the owner of nodes like New last hours of cb, CB stats, Chatterbox KARMA support, Chatterbot update, Chatterbot update (same node name, different conversation), (and the cavac-replies following), would those XP immediately transfer from cavac to chatterbot? Or would the bot only receive new upvotes going forward and the original owner would keep the existing XP? Because if the XP transferred immediately, it might be worth the quick-boost to the bot's XP to chown those nodes. Of course, such an XP-transfer from a chown would minorly reduce cavac's duly-earned XP, so such a transfer would have its cost, and thus the chown/XP-exchange should only happen if cavac and the gods both agree to the change in XP...

        Then again, the gods do have the power to grant fiat XP as well, so maybe such convoluted machinations aren't worth it when a much simpler fix would suffice.

[reply]
Re^8: super slow
by Danny (Chaplain) on Aug 23, 2024 at 20:29 UTC
    Might be good to reverse order the days and times so "now" is at the top.
[reply]

In Section Perl Monks Discussion