Repository navigation
Lista de mesas solo para quien la mira - #15
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
La lista de mesas se mandaba entera a todos los conectados (también a los que estaban jugando) en cada alta, unión, inicio y fin de mesa, y duplicada con el evento viejo
lobbiesList. Con 200 mesas eran ~24 MB por cambio y el server se trababa con ~100–200 partidas.lista: entra quien se conecta o pide la lista sin estar sentado; sale al crear, unirse o reconectarse a una mesa.lobbiesList, que el frontend no usa.Prueba de carga en el homelab (bots de 4 jugadores, 1–3 s por jugada):
Por encima de ~1500 partidas el límite pasa a ser un núcleo de CPU (Node es de un hilo).