Correzione refuso e periodo di attesa casuale per API Piracy Shield #36
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
…e i server API di Piracy Shield con richieste concorrenti.
|
Riduce gli errori di timeout durante le interrogazioni periodica dell'API di Piracy Shield |
iz7crx
changed the title
|
In realtà lo avevamo già provato ma non risolve nulla, purtroppo i timeout sono frequenti, per poter essere sicuri di prendere i ticket e lavorarli, consigliamo di mettere il cron ogni 2 minuti |
|
Accedere tutti contemporaneamente ogni 2 minuti - oppure ogni 10 - non risolve il problema della concorrenza delle richieste al secondo 00 del minuto pianificato. Nella proposta abbiamo introdotto un semplice ritardo casuale per distribuire le richieste nel tempo. Lato nostro sta andando meglio. |
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.
È un piccolo errore, ma insidioso perché legato al cron.