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

Increase database plan #3

Open
niconoe opened this issue Jul 14, 2023 · 1 comment
Open

Increase database plan #3

niconoe opened this issue Jul 14, 2023 · 1 comment
Assignees

Comments

@niconoe
Copy link
Member

niconoe commented Jul 14, 2023

I find the production website (https://alert.riparias.be) feels somewhat slower than before.

This is not a surprise, given that:

  • We've initially hosted it on relatively cheap/low end AWS services
  • The number of observations has been multiplied by ten recently. Also more and more users and alerts in the system.

The bottleneck is probably the database (hosted on RDS). I was wondering if INBO is willing to pay for a larger RDS instance in order to improve the user's experience? @damianooldoni: can you check with the IT OPS which RDS plan is used in production, how it would cost to take a larger one and if the financial side agree to this?

Thanks

@damianooldoni
Copy link
Collaborator

damianooldoni commented Sep 11, 2023

Waiting for a bigger infrastructure, see this short term solution: riparias/gbif-alert#92 (comment). Showing data from the last 10 years is really more than enough for an early alert application 😄
Of course the problem persists on the medium/long term as the number of occurrences per year typically increases due to the spread of IAS and increase of research effort. Also we could add more species to the species list...

@damianooldoni damianooldoni mentioned this issue Sep 19, 2023
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants