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

Investiguate improvements to the follow endpoints #6166

Open
loicmathieu opened this issue Nov 28, 2024 · 0 comments
Open

Investiguate improvements to the follow endpoints #6166

loicmathieu opened this issue Nov 28, 2024 · 0 comments
Labels
area/backend Needs backend code changes enhancement New feature or request kind/cooldown Great candidate for the cooldown period

Comments

@loicmathieu
Copy link
Member

Feature description

From the webserver we have two follow endpoints to follow and execution running, or execution logs.
Those use the queue so, in JDBC, they poll the database using a lock each 25ms!

We should revisit that as it causes unnecessary load on the database on the most used tables: queues.

Possible solutions:

  1. poll the executions or the logs table directly, this can be problematic as those are indexed async (except executions in JDBC)
  2. use a poll without locking and with a higher period: this means we would expose internal detail of the polling mechanism to the webserver
@loicmathieu loicmathieu added area/backend Needs backend code changes enhancement New feature or request kind/cooldown Great candidate for the cooldown period labels Nov 28, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Issues Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes enhancement New feature or request kind/cooldown Great candidate for the cooldown period
Projects
Status: Backlog
Development

No branches or pull requests

1 participant