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) 5월 30, 2022, 3:33오후 3

rebake가 필요한 모든 게시글에 대해 post.rebake!을 호출하기만 하면 됩니다.
baked_version을 건드릴 필요는 없습니다.

글		댓글	조회수
My journey into a massive posts rebake job Self-hosting	35	4880	7월 10, 2024
Rake posts:rebake_incremental (feature request) Feature	2	843	4월 22, 2020
"rebake old posts count" option is a bit confusing Bug	4	575	2월 23, 2021
Is it necessary to rebake all posts during major version releases? Support	1	790	3월 28, 2020
Slow rebake script to avoid overwhelming your server Migration	4	237	11월 13, 2025

모든 게시물 다시 렌더링 최적화

Related topics