feat: Phase 0 concurrent upload pipeline and benchmarks #27
No reviewers
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-card-creation#27
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/render-pipeline-optimization"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Phase 0 render pipeline optimization — card-creation side (WP-00, WP-04, WP-05).
Companion to paper-dynasty-database PR #94 which handles the server-side changes (persistent browser, self-hosted fonts, lifespan hooks).
WP-00: Baseline Benchmarks
scripts/benchmark_render.sh— automated render timing script with--quickand--prodmodesscripts/benchmark_results.txt— baseline measurements (~2.0s avg per card)WP-04: Concurrent Upload Pipeline (
pd_cards/core/upload.py)for x in all_players:loop withasyncio.gather+Semaphore(8)run_in_executorfetch_card_imagetimeout from 6s → 10s--concurrency / -jCLI flag (default: 8)WP-05: Legacy Upload Script (
check_cards_and_upload.py)CONCURRENCY = 8constant, timeout increase, progress reportingResults (with server-side Phase 0 deployed)
Supersedes
Test plan
pd-cards upload s3 -c "2005 Live" --limit 10 -j 8completes without errorscheck_cards_and_upload.pyruns concurrently without errors--concurrency 1behaves like sequential (regression safety)Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com