fix(genre-tree): cap full-list page fetches at 4 concurrent - #178
Merged
Merged
Conversation
Fetching all remaining pages in parallel sent 17 concurrent requests for the canonical tree, OOM-killing grow-front's proxy container (502s). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
useListFullGenrePlaylistsfetched every remaining page at once throughPromise.all. For the canonical tree that is 17 parallel requests. On staging they OOM-killed grow-front's 96m proxy container, and the browser got 502s on/api/grow-proxy/genre-playlists?page=N.The remaining pages now go through a pool of 4 workers. Results stay in page order and the error behaviour is unchanged.
Tests
Related infra mitigation: BehindTheMusicTree/infrastructure#206 (mem_limit 96m to 192m).
🤖 Generated with Claude Code