-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Bug] - Slow speed of navigation around ODP #52
Comments
@shubham-mahajan please can the details be added to the ticket above regarding the page cashing to improve navigation of the ODP. |
@shubham-mahajan please could we have some details on here regarding the page cashing? aimed at improving navigation and speed of the site. |
@NHSBSA-Open-Data The caching is for the static assets like css, js etc not for the entire page. What it will affectWhen we cache the statics, we are not loading the fonts, css, js etc everytime but the browser will store that in the cache which prevent extra overhead of loading the files from the server. We are not caching the whole page, means the data will come fresh. The slowness of the portal is linked to the usage also, which will be taken care with the architectural change of separating the Datastore API and the CKAN API's |
afaik this was done in staging but not in prod. @shubham-mahajan can you confirm the status of separating the Datastore API and CKAN API? |
@Daniellappv Yes, This is done in staging but not in prod |
Hi @NHSBSA-Open-Data Can we go ahead with enabling the cache, along with the architectural change of separating the Datastore API and the CKAN APIs in production as well? |
Overview
We have had reports of slow navigation speeds between pages on the ODP. particularly when going between dataset which have a large amount of data or many resources.
What is affected?
Sitewide Open Data Portal
Timeframe of solution
Minor fixes to be rolled out over the next month.
Resolution date
2024/2025 Quarter 1
Solution Details
What went wrong?
Why did it happen?
The solution implemented
How are we ensuring this does not happen again
The text was updated successfully, but these errors were encountered: