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

Extract personas performance issue #1634

Open
Dantemss opened this issue Mar 15, 2024 · 0 comments
Open

Extract personas performance issue #1634

Dantemss opened this issue Mar 15, 2024 · 0 comments

Comments

@Dantemss
Copy link

Dantemss commented Mar 15, 2024

What version were you using?

v7.1.1 (open source) - it doesn't seem to allow me to change the issue label

What steps can we follow to reproduce the behaviour?

Have a Learning Locker instance with several million statements (using DocumentDB in my case).

What is the actual behaviour?

The following query shows up in DocumentDB performance insights as taking nearly 100% of the database IO for a few hours at a time, causing responsiveness issues:
Screenshot 2024-03-15 at 10 46 00 AM

It then disappears for several hours. Reading the worker code, it doesn't seem like it intends to update a lot of statements at once, since updates are only supposed to happen when personas are created for the first time, so I'm not entirely sure why this situation is happening.

What is the expected behavior?

If I understand right, personas should only be created when the first few statements are received for each user, so these mass updates shouldn't happen.

Is there any additional information that will help us replicate/understand the problem?

Let me know if there's more information that I can provide.

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

1 participant