Browse Source

Refactor rebuilding after posts, finish reply requests before rebuilding index

This provides massive improvements to perceived post times as it doesn't wait for the entire board to rebuild index before confirming to the user that the post was made
pull/68/head
discomrade 1 year ago
parent
commit
e906ac7451
  1. 35
      post.php

35
post.php

@ -1449,24 +1449,33 @@ function handle_post(){
));
}
if ($config['try_smarter'] && $post['op'])
$build_pages = range(1, $config['max_pages']);
if ($post['op'])
if ($post['op']) {
clean($id);
if ($config['try_smarter'])
$build_pages = range(1, $config['max_pages']);
event('post-after', $post);
buildIndex();
// We are already done, let's continue our heavy-lifting work in the background (if we run off FastCGI)
if (function_exists('fastcgi_finish_request')) {
@fastcgi_finish_request();
}
event('post-after', $post);
buildIndex();
// We are already done and post is visible to others, let's continue our heavy-lifting work in the background (if we run off FastCGI)
if (function_exists('fastcgi_finish_request')) {
@fastcgi_finish_request();
}
if ($post['op']) {
rebuildThemes('post-thread', $board['uri']);
} else {
event('post-after', $post);
// We are already done and post is visible to others, let's continue our heavy-lifting work in the background (if we run off FastCGI)
if (function_exists('fastcgi_finish_request')) {
@fastcgi_finish_request();
}
buildIndex();
rebuildThemes('post', $board['uri']);
}
}

Loading…
Cancel
Save