Repository navigation
Rate-limit the size of faup1090 (fatsv) updates - #328
Draft
mutability wants to merge 1 commit into
Draft
mutability wants to merge 1 commit into
mutability wants to merge 1 commit into
Conversation
Try to generate no more than ~ 10kB/s of fatsv output. If we exceed that when generating output, stop generating more and remember where we were in the aircraft list, then resume from that point on the next update. Any aircraft that get delayed like this will just have their reporting times pushed out a bit, the actual data generated should still be fine (and up to date at the point of generation) This should help with high-traffic sites, especially on restart where suddenly every visible aircraft wants to generate a report at the same time.
This file contains hidden or 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.
Try to generate no more than ~ 10kB/s of fatsv output. If we exceed that when generating output, stop generating more and remember where we were in the aircraft list, then resume from that point on the next update.
Any aircraft that get delayed like this will just have their reporting times pushed out a bit, the actual data generated should still be fine (and up to date at the point of generation)
This should help with high-traffic sites, especially on restart where suddenly every visible aircraft wants to generate a report at the same time.
PR checklist
dev(notmaster)