Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement background batch processing for sitemap updates instead of locking #15783

Open
Piedone opened this issue Apr 17, 2024 · 0 comments
Open

Comments

@Piedone
Copy link
Member

Piedone commented Apr 17, 2024

Is your feature request related to a problem? Please describe.

Sitemaps are stored in a single document, thus concurrent updates to it (what happens if you click Publish on two content items at the same time) will cause an exception, see #15743. To overcome this, #15777 introduced locking. While this fixes the immediate issue, for sites where content items are published rapidly, this may result in degraded performance when saving content items.

Describe the solution you'd like

Implement a task-based background processing like what we have for indexing. However, this needs to be checked, because while this can reduce the latency of content publishing, it may increase overall load on the DB and thus reduce throughput.

Describe alternatives you've considered

Locking and background batch processing are the only two solutions I can think of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants