You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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...
I find the production website (https://alert.riparias.be) feels somewhat slower than before.
This is not a surprise, given that:
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
The text was updated successfully, but these errors were encountered: