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

OBAS performances are too slow to be used #898

Closed
jborozco opened this issue May 17, 2024 · 2 comments
Closed

OBAS performances are too slow to be used #898

jborozco opened this issue May 17, 2024 · 2 comments
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved The issue has been solved
Milestone

Comments

@jborozco
Copy link

Description

Globally all screens are too slow to load, few examples:

  • Home dashboard
  • List of simulations
  • List of teams in simulation settings

This makes the application unusable for our clients and give the impression that some screens are broken when they are actually just loading like in the case of the list of teams in simulation settings.

@jborozco jborozco added bug use for describing something not working as expected critical use to identify critical bug to fix ASAP labels May 17, 2024
@jborozco
Copy link
Author

Sorry I opened the previous ticket in OCTI 😅

@RomuDeuxfois
Copy link
Member

After several tests, this seems to be fixed.
There is still work to be done to improve the overall performance of the application.

Dimfacion added a commit that referenced this issue May 28, 2024
* [backend] Switching get scenarios, statistics and exercises to raw native query (#898)
@jborozco jborozco modified the milestones: Release 1.1.0, Release 1.2.0 Jun 13, 2024
@jborozco jborozco closed this as completed Jul 3, 2024
@SamuelHassine SamuelHassine added the solved The issue has been solved label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved The issue has been solved
Projects
None yet
Development

No branches or pull requests

8 participants