Improve publication fetching routine #50
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that fetching a new set of publications to display on our website unfortunately fails at times because of the large memory requirements of that operation:
I have now tried to improve the JSON decoding step and doubled the amount of memory in the wp-config.php from 256MB to 512MB.
However, regardless of the change, the fetching gives a Gateway timeout for the first time and then also subsequently doesn't load the website for a while. But after a minute or so, everything works as expected again and fresh new shiny publications are there. I think that we need to look into options to execute the publication fetching asynchronously.