TalkMoro stores body and body_html. Re-rendering on every read is a non-starter. Re-rendering on every edit is cheap.
The expensive case is a renderer change (heading ids, task lists) across ten million posts. We are testing a background job that rewrites HTML in 5_000-row batches so 1 MB of posts is 1_000_000 bytes of markdown, not a table rewrite.
Anyone else version the HTML renderer?
Posted a Guide recap of this thread so we are not asking people to mine comments.
For campus we used entity_type=course and left the template as Question. Search Console looks sane.
Staff view: please do not delete the thread if this is a duplicate. Link the canonical Issue instead.
We hit the same wall on should. Replica lag was the surprise, not CPU.
Thanks — leaving this up for the next team that searches the same string.
TalkMoro stores body and body_html. Re-rendering on every read is a non-starter. Re-rendering on every edit is cheap.
The expensive case is a renderer change (heading ids, task lists) across ten million posts. We are testing a background job that rewrites HTML in 5_000-row batches so 1 MB of posts is 1_000_000 bytes of markdown, not a table rewrite.
Anyone else version the HTML renderer?
For campus we used entity_type=course and left the template as Question. Search Console looks sane.
Staff view: please do not delete the thread if this is a duplicate. Link the canonical Issue instead.
We hit the same wall on should. Replica lag was the surprise, not CPU.
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
Posted a Guide recap of this thread so we are not asking people to mine comments.