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

Investigate bad performance / timeouts on Open Klant v2 #323

Open
stevenbal opened this issue Jan 23, 2025 · 1 comment
Open

Investigate bad performance / timeouts on Open Klant v2 #323

stevenbal opened this issue Jan 23, 2025 · 1 comment
Labels
bug Something isn't working triage

Comments

@stevenbal
Copy link
Collaborator

Product versie / Product version

latest / 2.4.0

Omschrijf het probleem / Describe the bug

Via slack from @swrichards

Just a note that we've integrated our Open Inwoner test environment with the OpenKlant2 sandbox, and we're getting a lot of slow (30s+) responses and quite frequent timeouts on OIP endpoints that synchronously interact with OK2. I should also note that this is not because the of the volume of data, most of the list endpoints are empty. Not especially urgent, we can just disable it for the moment, but it'd be worth figuring out of this is a resource or configuration issue. (I had similar issues last week, so I doubt it's a transient thing)

Image

Stappen om te reproduceren / Steps to reproduce

No response

Verwacht gedrag / Expected behavior

No response

@swrichards
Copy link
Contributor

I should add that @Tiho0135 had a look and noticed the container had been running for several months. Once he restarted the container the response times returned back to normal, which suggests may point to some kind of memory leak or descriptor shortage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
Status: Triage
Development

No branches or pull requests

2 participants