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

Consolidation tasks may consume all CPUs and defer other consolidations #156

Closed
valeriansaliou opened this issue Jul 10, 2019 · 2 comments
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@valeriansaliou
Copy link
Owner

Issue observed at Crisp's scale (https://crisp.chat/); it's been a week that after a smooth sailing, our Sonic instance started consuming A LOT of CPU, on consolidation tasks (first guess).

An investigation of the heaviness / slowdown needs to be proceeded, and the performance issue needs to be fixed.

@valeriansaliou valeriansaliou added the bug Something isn't working label Jul 10, 2019
@valeriansaliou valeriansaliou self-assigned this Jul 10, 2019
@valeriansaliou valeriansaliou added this to the v1.2.2 milestone Jul 10, 2019
@valeriansaliou
Copy link
Owner Author

That may also be due to RocksDB, need to investigate.

@valeriansaliou
Copy link
Owner Author

valeriansaliou commented Jul 12, 2019

Targets:

  • When pushing new words to FST graph, check if FST is already over limits or not (do nothing if over limits, if push);
  • Attempt to optimize FST consolidation algorithm;

valeriansaliou added a commit that referenced this issue Jul 12, 2019
Signed-off-by: Valerian Saliou <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant