Optimiser la generation de grille et les requetes aleatoires #13
Labels
No labels
area: auth
area: deps
area: frontend
area: gameplay
area: import
area: infra
area: product
area: tests
priority: P0
priority: P1
priority: P2
priority: P3
type: bug
type: chore
type: feature
type: infrastructure
type: performance
type: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: thibaud-lclr/ltbxd-actorle#13
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
1. Le souci
La generation de grille combine plusieurs tirages aleatoires et des requetes couteuses (
ROW_NUMBER,ORDER BY RANDOM(), retries multiples). Cela risque de mal scaler quand le catalogue d'acteurs grossira.2. Proposition de solution
Revoir la strategie de selection des acteurs/indices pour limiter les scans couteux et les retentatives complètes.
3. Proposition d'implementation