-
• #103
ditto
-
• #104
+1
-
• #105
Yup
-
• #106
No, it's fine.
-
• #107
Seems a bit problematic again
-
• #108
About an hour ago, when you wrote this, there were some issues.
Specifically 109 pages returned a HTTP 500 error, which all seem to indicate issues on the server.
Having looked into it, it looks like memcached failed, which caused a thundering herd of queries to the database, which then backed up for 10 minutes, and thus caused timeouts.
-
• #109
Memecache..
-
• #111
this page just fully loaded in 381 milliseconds.
so I went and checked the last 30 days to see if there is a slowdown recently... but nope, 95th percentile is still barely over 1 second, and 90th percentile is solidly around 500 milliseconds.
that's a measure of "request time" from the web server, and so it includes the time to send to the client, meaning it reflects the network speed of all clients requesting things from LFGSS too.
data says that the problem isn't a general one on our side, so it must be on your side.
1 Attachment
-
• #112
Cheers
For some reason pages are slow for me on Lfgss on my laptop but BBC website is prompt.
-
• #113
unless Google Fonts is slow... because I browse the web with fonts turned off.
so maybe they're slow... but even if they are, they should be cached and it would still be fast.
so no... it's you :)
-
• #114
Oh... if a page is full of third party images, then that might be slow 🤷
@Velocio
Many error messages this evening.