in reply to Re: perlmonks.org still/again slow - weird Febraury 12th 2025
in thread perlmonks.org still/again slow
chatterbot was pretty much unable to communicate with PM. It seems it was occasionally able to update some pages, but it was pretty much missing out on getting most of the posted chatterbox messages:
# select logtime, username, message from chatterbot.inbox where logtim +e > '2025-02-11 14:30' order by logtime; logtime | username | + message ----------------------------+----------------+------------------------ +--------------------------------------------------------------- 2025-02-11 14:32:44.782183 | choroba | Getting timeouts... 2025-02-12 07:59:24.645271 | Discipulus | good morning and nice c +amelday! 2025-02-12 08:50:38.607121 | Discipulus | still.. really weird 2025-02-12 09:51:14.57602 | Discipulus | now both 200 OK 2025-02-12 16:14:51.780973 | hippo | :-( This is painfully s +low. Will try again tomorrow. 2025-02-13 15:41:13.509351 | marto | hey all 2025-02-13 16:31:43.35478 | hippo | ... aaaaaaaaand we're b +ack. Have the bots given up or are they just having their tea?
At least on and around the 12th of February, this doesn't look like a technical problem with PM per se. The failure rates seem to rise over some hours, see pm server stats. If PM is unreachable, you can also view the stats on my external site.
Please note, though, that chatterbot only logs that something has gone wrong during a web request. It currently doesn't log what exactly has gone wrong. Also, chatterbot runs as a cyclic executive¹. It tries to do the webcalls at a certain frequency, if some (or all) webcalls take a long time to complete or run into timeout, the number of webcalls per hour sharply decreases.
I technically do log the status and time taken for every webcall and use that to calculate the per-hour stats for the web pages. I doubt this will be much help, but i certainly can provide that data if it seems useful.
¹ A form of cooperative multitasking within a single program. Wikipedia. My server runs quite a few of these "workers". All of the chatterbot code is in a single worker, because it doesn't make sense to parallelize PM tasks.
|
|---|