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
IATI Publisher's user base continues to grow and we need to ensure the tool can handle this with a minimum level of performance.
Over the year Dec 2023 - Nov 2024, there were on average 11 new organisations (and 18 new users) registering each month on IATI Publisher. This increase in usage is gradual, but we may also see influxes of new users in 2025 due to migrations from other publishing tools.
We want to be able to monitor user volumes and time taken for common processes such as sign in, page loads, activity publication, and data import. This will allow us to monitor monthly trends and detect slow performance before it becomes a problem.
Possible tasks:
Monitor volumes of active vs. total registered users per month to track usage over time. More registered users are not necessarily a problem if the number of users actively using the tool each month stays stable.
Implement user-centric monitoring of performance for key pages. For example, how long does it take between clicking the "Sign in" button and the page finishing loading? Or, how often does a page appear empty to a user because a query to get the activities / transactions / results has timed out?
Ensure automated alerts and logs are in place to anticipate or troubleshoot problems relating to usage capacity.
This issues relates to #1643 (code analysis and structural improvements to prepare for more users)
The text was updated successfully, but these errors were encountered:
IATI Publisher's user base continues to grow and we need to ensure the tool can handle this with a minimum level of performance.
Over the year Dec 2023 - Nov 2024, there were on average 11 new organisations (and 18 new users) registering each month on IATI Publisher. This increase in usage is gradual, but we may also see influxes of new users in 2025 due to migrations from other publishing tools.
We want to be able to monitor user volumes and time taken for common processes such as sign in, page loads, activity publication, and data import. This will allow us to monitor monthly trends and detect slow performance before it becomes a problem.
Possible tasks:
This issues relates to #1643 (code analysis and structural improvements to prepare for more users)
The text was updated successfully, but these errors were encountered: