Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance: Step muy lento para ATLAS #29

Open
pcastelln opened this issue Mar 21, 2023 · 2 comments · May be fixed by #31
Open

Performance: Step muy lento para ATLAS #29

pcastelln opened this issue Mar 21, 2023 · 2 comments · May be fixed by #31
Labels
bug Something isn't working

Comments

@pcastelln
Copy link
Contributor

pcastelln commented Mar 21, 2023

No está claro qué está pasando, pero el step está produciendo y los logs están activos. Sin embargo el lag no deja de crecer en el cluster

Edit: el lag si disminuye, solo que el step es muy lento

@pcastelln pcastelln added the bug Something isn't working label Mar 21, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in ALeRCE Project Mar 21, 2023
@pcastelln pcastelln moved this from 🆕 New to Backlog in ALeRCE Project Mar 21, 2023
@pcastelln
Copy link
Contributor Author

Aparentemente tiene que ver con el cálculo de header, hay que ver si es necesario en primer lugar

@dirodriguezm
Copy link
Contributor

Refactorizar que el ra y dec no se calculen con el header, si no que con la alerta.

@dirodriguezm dirodriguezm changed the title Lag del step crece sin límites para ATLAS Performance: Step muy lento para ATLAS May 5, 2023
@dirodriguezm dirodriguezm moved this from Backlog to 🆕 New in ALeRCE Project May 8, 2023
@dirodriguezm dirodriguezm linked a pull request May 31, 2023 that will close this issue
@dirodriguezm dirodriguezm moved this from 🆕 New to Backlog in ALeRCE Project Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants