-
Notifications
You must be signed in to change notification settings - Fork 7
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
API slow when retrieving pipelines #531
Comments
If possible it shall be fixed in release branch to include into 2.2.0. If fix is too complex then via feature branch. |
I investigated this issue and experienced similar problems, which were probably connected with memory issues. However when I added more memory to Tomcat, I had no performance issues at all. I added some more pipelines (~100 in database) and was able to obtain them via master API in ~30 ms. I tried to test this also on eDemo DEV environment, where CKAN and UV are on separate servers, but I never got timeout. (UV has ~80 pipelines in database) I could not find any performance issue in code either. Database query for getting pipelines is not optimal as it is JOIN of 3 tables but with such small tables it should not be an issue. So conclusion: From what I tested I would suspect that this is related to memory issues with master component. To detect precisely where the memory issue is, it would require much more thorough testing. As a workaround I would increase memory for Tomcat, I used this configuration and had no issue and everything worked quckly:
|
Probably same issue is #431 |
It is reported that UV is slow when retrieving list of pipelines (86 pipelines took more then 5 seconds).
See OpenDataNode/open-data-node#213 for more details
The text was updated successfully, but these errors were encountered: