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

Optimize schedule save #1114

Open
MinhxNguyen7 opened this issue Jan 13, 2025 · 0 comments
Open

Optimize schedule save #1114

MinhxNguyen7 opened this issue Jan 13, 2025 · 0 comments
Labels
backend bug codefix Refactoring or improving the codebase high High priority issue

Comments

@MinhxNguyen7
Copy link
Member

Description

  • Large schedules can take a long time to save, exceeding the old lambda limit of 5 seconds, and sometimes exceeding the current limit of 10 seconds.
  • Saves take such a long time because of operations on the database, which are not very efficient right now.
  • This is probably because we delete all of the user's data and put it back in every save.
@MinhxNguyen7 MinhxNguyen7 added bug codefix Refactoring or improving the codebase high High priority issue backend labels Jan 13, 2025
@github-project-automation github-project-automation bot moved this to Backlog 🥱 in AntAlmanac Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug codefix Refactoring or improving the codebase high High priority issue
Projects
Status: Backlog 🥱
Development

No branches or pull requests

1 participant