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

[Bug][Optimisation] Selecting year in map causes excessive memory usage. #402

Open
shaman007 opened this issue Nov 14, 2024 · 2 comments
Open

Comments

@shaman007
Copy link
Contributor

When a year is selected, the app goes to the URI 'from the beginnig of the year to it's end', i.e.:

https://dawarich.andreybondarenko.com/map?end_at=2020-12-31T23%3A59&start_at=2020-01-01T00%3A00&year=2020

This causes excessive memory usage and the container fails with sig 137. Freshely started container can handle the year.

Wouldn't it be better to default to some month, like Jan? Ideally the 'year' should be loaded with low granularity, i.e. only approximate dots on the map that is zoomed maximum away. With all the dots default zoom looks like just a mess of lines.

@shaman007
Copy link
Contributor Author

UPD:

rendering map in "simplified" mode is way better. Maybe make it default?

@Freika
Copy link
Owner

Freika commented Nov 15, 2024

Maybe make it default?

It's good idea, I might do just that!

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