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

Issues with alert.riparias.be Loading Time and Forbidden Access (403) #21

Open
fjasteen opened this issue Apr 23, 2024 · 2 comments
Open

Comments

@fjasteen
Copy link

fjasteen commented Apr 23, 2024

Experiencing significant delays in loading the alert.riparias.be webpage, with load times from over a minute. Additionally encountering Forbidden (403) errors when attempting to access the site (after login screen). The following issues have been identified:

  1. Loading Time Delay: Users across multiple devices (three separate laptops) and browsers (Edge and Chrome) have reported excessive loading times. Even after clearing the Chrome cache, the issue persists.
  2. Forbidden (403) Errors: I have encountered Forbidden errors, both in regular browsing mode (Edge & Chrome) and incognito mode (Chrome)
  3. No Improvement with Different Accounts: Switching to alternative accounts does not alleviate the loading time delay or resolve the Forbidden errors
  4. Slow Initial Popup: In some instances, the initial popup, particularly the species selection, loads extremely slowly, resulting in delayed display of labels and species names lost.
  5. Long Page Load Times: Various pages within the website, including the front page login and area selection, take several minutes to load
  6. On some occasions pages do load, but this seems unrelated to size of request (# polygons/species)
  7. fi. loading the parcels from DVW costs 3 minutes, and loading the tiles costs another minute, for a total of 180 observations
@fjasteen
Copy link
Author

image

@niconoe
Copy link
Member

niconoe commented May 14, 2024

Thanks a lot for the detailed report, @fjasteen!

This is due to the fact that GBIF alert (the tool behind the site) doesn't currently deal very well with the large amount of data (users / alerts / observations) in the system. We plan to structurally fix that, but we might have to circumvent the issue first (by importing only recent data from GBIF first) because I might not have the availability to fix it immediately.

The issue (and progress) is tracked here, if you're curious about it: riparias/gbif-alert#273 (comment)

Sorry again for the inconvenience and hope to fix that soon!

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