[02:56:22] 10MediaWiki-Core-Team: Run MassMessage to contact user talk pages of all affected accounts - https://phabricator.wikimedia.org/T90820 (10Krinkle) [02:58:31] * Krinkle giggles [20:09:31] Amir1: There's an idea I scribbled down during a conversation a while back, about simplifying Rdbms read-only logic and moving it out of page view requests. [20:09:33] > - 4 Aug 2022: Rdbms reduce read only runtime discovery to write queries only. But check for cache both ways. [20:10:35] that sounds doable [20:10:56] feel free to make a patch or ticket [20:11:05] I'd be happy to see it through :P [20:11:08] What do you think about that? So passive isReadOnly checks will deterministically not produce master connections if called on requests that only use replicas (i.e. GET), but assuming you have any cache defiend (not CACHE_NONE) and the wiki is non-dead (has some requests that use master conns), then the info will be read from those keys and applied. [20:12:20] "configured" readonly mode would remain always accurately reflected of course [20:12:43] yeah, my only comment here is a bit different but I think we should move away from bagostuff or caching in rdbms in genera, the caching should be left to the higher levels [20:13:02] one big reason is that bagostuff and rdbms libraries have cyclic dependencies [20:13:26] bagostuff needs rdbms via sql bagofstuff and rdbms library needs caches [20:13:55] right [20:13:56] so we can end up in a mess if a cache used by the db object actually end up being a db [20:15:36] yeah, I don't think we can avoid that between components without making components very small, but I think you mean specificlalyt between BagOStuff and LoadBalancer/IDatabase. That seems avoidable yeah. For example, we moved ReadOnlyMode to Rdbms, but the cache is lower-level right now inside IDatabase. We can move that out to the ROM class to start with. [20:16:08] * Krinkle creates task [20:16:16] yeah [20:17:00] Amir1: I'm creating this task under T302623, where I noticed T280604 still open. [20:17:01] T280604: Post-deployment: (partly) ramp parser cache retention back up - https://phabricator.wikimedia.org/T280604 [20:17:01] T302623: FY2022-2023: Improve Backend Pageview Timing - https://phabricator.wikimedia.org/T302623 [20:17:37] we are waiting for the hardware to be cabled in the dc and then we expand PC and then after a while I will ramp it up [20:17:47] I want to do one thing on PC at the time [20:17:50] ack, do you mind saving that on-task? [20:17:57] sure