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…

[изображение] 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 righ…

[изображение] 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).

Оптимизация повторной публикации всех постов

Поддержка

RGJ (Richard - Communiteq) 30.Май.2022 15:33:17 3

Вы можете просто выполнить post.rebake! для каждого поста, требующего rebake.
Нет необходимости возиться с baked_version.

Тема		Ответов	Просм.
My journey into a massive posts rebake job Self-hosting	35	4880	10.07.2024
Rake posts:rebake_incremental (feature request) Feature	2	843	22.04.2020
"rebake old posts count" option is a bit confusing Bug	4	575	23.02.2021
Is it necessary to rebake all posts during major version releases? Support	1	790	28.03.2020
Slow rebake script to avoid overwhelming your server Migration	4	237	13.11.2025

Оптимизация повторной публикации всех постов

Связанные темы