Skip to content

Conversation

@Naramsim
Copy link
Member

No description provided.

Copy link
Member

@phalt phalt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A wider gap to give it more time to boot up?

@Naramsim
Copy link
Member Author

The problem was that a 1s interval is too frequent, especially for the graphql machine. I saw that pg_isready consumes quite a lot of CPU and was slowing down the entire machine especially during the gql data update procedure.

@Naramsim Naramsim added the no-deploy Instructs the updater-bot not to deploy this PR label Dec 21, 2024
@Naramsim Naramsim merged commit 4e3b38d into master Dec 21, 2024
3 of 4 checks passed
@pokeapi-machine-user
Copy link

This Pull Request won't be deployed since the label no-deploy was found in its meta-data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-deploy Instructs the updater-bot not to deploy this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants