Ryan Barrett
Ryan Barrett
Interesting, temporarily disabling AP outboxes for #1248 cut both our datastore read and frontend instance costs in half:
The drop in datastore read cost due to outboxes was mostly queries, as we'd expect.
This specific cost is our datastore, ie database. Not related to external fetches. (Which we don't really do during outbox rendering anyway.)
Ah! I haven't looked specifically or tried to correlate, but all the drop here was in queries, and object fetches only do lookups.
Starting to look at this again...
Re-running analytics from https://github.com/snarfed/bridgy-fed/issues/1149#issuecomment-2259178748 : Datastore API calls by method: Lookups by kind: Queries by kind: Queries by filter: ...somehow we're back to overdoing copy queries again?!
Object lookups by type:
Goddammit, this bit me again just now, shipped #1205 via 98098aeabbeffdd2c367cfe6787f89dc1bb48f58 with a bug, the id of the sent DM was right but the contents were wrong. Argh. Prioritizing!
Sigh, yes. Good example of why facet/index-based rich text is more difficult to work with than markup-based rich text, and why much of the standards community, eg W3C, has moved...