[01:49:41] [1/2] There were some discussions in the Weird Gloop server about performance which led to us discovering that [micro_bench.php](https://github.com/php/php-src/blob/master/Zend/micro_bench.php) takes around 10 seconds on our servers (test151, mwtask161) but between 1 to 2.5 seconds on other hosts. It's quite mysterious how our servers are so slow in single-threaded workloads even if [01:49:41] [2/2] they are from 2017. Infra might know better about this though. [10:07:15] [1/2] https://meta.miraheze.org/wiki/Tech:Performance [10:07:16] [2/2] Draft page on improving performance. There's a lot more to be said, but I'll just write what I know for now. [14:49:49] [1/3] > Filter requests that are "Served by origin" and ignore ones that are already cached or blocked by Cloudflare. [14:49:49] [2/3] You can also do this on Analytics & logs > HTTP Traffic by removing Cache status `Hit` and `None` (blocked requests are `None`) [14:49:49] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1491449995772039238/image.png?ex=69d7bc8c&is=69d66b0c&hm=f81a96cace5d394268041bc5eb1b3ece725910fb251bcde85b14782ad4378415& [15:02:09] does `Edge status code does not equal 403 Forbidden` work the same as `Cache status does not equal None` [15:57:52] [1/2] I'm gonna go with "mostly" [15:57:52] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1491467121819914450/image.png?ex=69d7cc7f&is=69d67aff&hm=36d8636f5df3909879ac94f1db459ddc9c45f29c59b2e539746064f3d9c5fc3a& [15:58:24] [1/2] actually theres a lot more in the other direction [15:58:24] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1491467255643508846/image.png?ex=69d7cc9f&is=69d67b1f&hm=6742a0224fe99ea5aacdc126749eac0c4cd0fe3ecf0572e4a701d582131d2ef6& [15:59:26] [1/2] these are all the edge status codes I see when filtering for "Cache status equals None" [15:59:27] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1491467518785753239/image.png?ex=69d7ccde&is=69d67b5e&hm=e2a4ac7222cde1c333d4d215d0356e986718186462fcbe8599cc87b6b7d83d1e& [19:25:29] btw, was looking at CVT feed and saw a funny link to a wiki: https://lostmediaru.miraheze.org/wiki/%d0%9 [19:26:02] Thanks for the tip. Do you find the "HTTP Traffic" page more useful? I always find it confusing that two analytics page exist with slightly different buttons. [19:36:05] I'm not really sure if there are any benefits to HTTP Traffic anymore. I think it used to have some extra drilldown stuff but maybe I just didn't know how the Security > Analytics page worked at the time. The notable advantage to the Security page is it has query strings, so you can do something like `Query string contains oldid` to see those [19:41:39] Yeah I remember a few months ago when I settled on the security page but I don't remember why I did that. Maybe query strings or a wider 3-column layout (on my laptop at least) were the reasons. [19:45:23] I guess the disadvantage is you only see requests, but the other types (Page views/Visits/API) are kinda garbage anyway [19:46:33] HTTP Traffic should show a sampled version of all traffic. Security only shows traffic that's triggered something WAF related. [19:46:50] Although Cloudflare's dashboard is getting significantly worse than it used to be [19:48:25] They seem to be showing the same data for me [19:51:13] That shouldn't be happening [21:24:07] btw Wikimedia moved echo-read-notifications from `user` to `*` recently because they realized temporary users exist and couldn't read their notifications [21:27:50] Interesting [21:28:02] Maybe make a subtask of the temp accounts one on Phorge [21:29:49] As I write this I realized I could just hit the ✏️ button on GitHub [21:32:43] https://github.com/miraheze/mw-config/pull/6366 [21:33:00] You could [21:33:33] I'll make that a tomorrow evening me problem [21:33:40] If no one else beats me [21:34:07] Oh hey they made public now I can finally read the backstory behind that right [21:34:43] Oh okay it was just about bot passwords and grants lmao [22:26:03] That was a vulnerability? I’ve been asking for that as a feature! [22:48:43] [1/4] Took care of 4 CirrusSearch requests as tech and 4 out of 4 ended up having issues, some worse than others. [22:48:44] [2/4] One wiki with the [classic issue](https://issue-tracker.miraheze.org/T15061#304371) which I fixed. [22:48:44] [3/4] Three wikis with terminated maintenance script runs which likely resulted in an incomplete search index. [22:48:44] [4/4] https://issue-tracker.miraheze.org/T14896#304372 [23:09:03] [1/2] me who just doesn't bother with cirrussearch [23:09:04] [2/2] you're not going to get cirrussearch and you're going to like it anyway [23:42:48] yeah I was confused too but Security page has query string [23:44:14] I think that depends on attack score. if you remove those constraints it should be the same