We have slightly under 30 million posts in our post table. This is making a rebake operation (after importing from a different forum software and making markdown modifications) rather untenable. I’m looking at how to optimize this. This particular call is taking hours to complete on my current test…

[imagem] Ghan: The field is an integer but is it necessary to reset it for all posts before we do any rebake operation? As I said, this single call takes hours to run because of the size of our post table. I have slightly modified the rebake code to instead make this call for each post right bef…

[imagem] Richard - Communiteq: No need to mess with baked_version . So that piece of code can be removed from the rake task? Why would it be there if it isn’t needed?

As far as I recall, the baked_version is there to cater for rebaking in case the Discourse rebake logic changed, (in contrast to when the raw content of the post has been changed).

Reassar todos os posts Otimização

Suporte

RGJ (Richard - Communiteq) Maio 30, 2022, 3:33pm 3

Você pode simplesmente emitir um post.rebake! para cada postagem que precisa de um rebake.
Não há necessidade de mexer com baked_version.

Tópico		Respostas	Visualizações
My journey into a massive posts rebake job Self-hosting	35	4879	10 de Julho de 2024
Rake posts:rebake_incremental (feature request) Feature	2	843	22 de Abril de 2020
"rebake old posts count" option is a bit confusing Bug	4	575	23 de Fevereiro de 2021
Is it necessary to rebake all posts during major version releases? Support	1	790	28 de Março de 2020
Slow rebake script to avoid overwhelming your server Migration	4	237	13 de Novembro de 2025

Reassar todos os posts Otimização

Tópicos relacionados