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 right before …

[图片] 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) 2022 年5 月 30 日 17:52 5

据我回忆，baked_version 的存在是为了在 Discourse 的重新烘焙逻辑发生变化时进行重新烘焙（与帖子原始内容被更改时的情况相反）。

话题		回复	浏览量
My journey into a massive posts rebake job Self-hosting	35	4879	2024 年7 月 10 日
Rake posts:rebake_incremental (feature request) Feature	2	843	2020 年4 月 22 日
"rebake old posts count" option is a bit confusing Bug	4	575	2021 年2 月 23 日
Is it necessary to rebake all posts during major version releases? Support	1	790	2020 年3 月 28 日
Slow rebake script to avoid overwhelming your server Migration	4	237	2025 年11 月 13 日

重新烘焙所有帖子优化

相关话题