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

dashboard_activity_list endpoint 504ing for one user #456

Open
robredpath opened this issue Jun 7, 2024 · 6 comments
Open

dashboard_activity_list endpoint 504ing for one user #456

robredpath opened this issue Jun 7, 2024 · 6 comments

Comments

@robredpath
Copy link

robredpath commented Jun 7, 2024

Placeholder issue to ensure visibility of this work; as this only affects one user (as far as we know) we don't want to share specific details in public.

I've emailed details to @cormachallinanderilinx .

@robredpath
Copy link
Author

Update after some discussion via email: this is due to the user in question having hundreds of activities on their dashboard, causing the query to time out. This is an issue with core CKAN. @cormachallinanderilinx is discussing with @EricSoroos to determine the scale of a potential fix.

@cormachallinanderilinx
Copy link
Collaborator

@robredpath we have a patch we are going to test out and see if gives us a performance improvement

@cormachallinanderilinx
Copy link
Collaborator

Hi @robredpath the patch is on applied on staging
Do you have access to their staging account and want to test it out there? Or are you happy for me to push it onto production?

@cormachallinanderilinx
Copy link
Collaborator

@robredpath

As discussed I tested this on staging and it took 4s with the patch
Without the patch it was taking 33s
Its not the same as production but its a significant increase, I think we should push it onto production at least?

@robredpath
Copy link
Author

@cormachallinanderilinx great - as long as there's no risk of unintended consequences then let's do it

@cormachallinanderilinx
Copy link
Collaborator

cormachallinanderilinx commented Jul 9, 2024

@robredpath The fixed was put onto production last week, do you know if this has improved things?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants