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

Performance Issues and Site Freezes when Trails are Rendering #234

Open
St0rml opened this issue Mar 30, 2025 · 1 comment
Open

Performance Issues and Site Freezes when Trails are Rendering #234

St0rml opened this issue Mar 30, 2025 · 1 comment

Comments

@St0rml
Copy link

St0rml commented Mar 30, 2025

Hey, I really enjoy Wanderer, thank you for your hard work!

Summary

At the moment, I have bad performance issues on the overview map. The map itself renders responsively, however, when I look at an area with trails in it (I have 22 total at the moment), I sometimes have to wait ~ 10s for the browser to render all the tracks and react to my inputs again. Then after every move on the map, when trails are visible, it freezes for a few seconds and so on.
I don't have a high-end PC, but at the moment Wanderer is the only website, where I really notice performance issue, hence I suspect it might an issue.

Details

Hard- and Software

  • i7-4790K CPU @ 4.00GHz
  • Radeon rx 6600 xt
  • Linux, Zorin OS 17.3 Core (Ubuntu 22.04-based)

Browsers tested on:

  • Firefox 136.0.4 (Flatpak), Clean install
  • Chromium 134.0.6998.165, Only Bitwarden-Addon

WebGL is enabled and my GPU is detected in Chromium.

Wanderer Version: v0.16.1

About the tracks

I noticed in another software, that my tracks for a 30km bike recording contain approx. 7500 Points. I don't know if that is normal or not though...

@slothful-vassal
Copy link

I can confirm, there are several performance issues. I'm running wanderer on a Synology NAS.
But I can't reproduce on my dev workstation.

The main problem seems, that always the whole database will be retrieved...
Sample: I had a long loading time, when press 'New Trail' until the page was loaded. After deleting my trail 'List', the loading time has been increased massively. First code review proves that: the whole list including all containing trails will be loaded when creating a new trail.
When opening the trail overview page, all trails will be loaded completely.

Maybe, there can be made some improvements.

Many thanks.

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