Replies: 2 comments 6 replies
-
Moving this to a discussion as I believe it's more a conversation on what's happening / how to improve rather than a single bug we can fix on the map I think it's simply because the map layout takes way more resources from the browser to render than the table does! It could also be the difference in number of records fetched; the table layout defaults to a pretty small page size, whereas the map layout renders way more points at the same time 🤔 |
Beta Was this translation helpful? Give feedback.
-
(Also, as per our other discussion in #13299, the current CSV import endpoint isn't really suited for big data imports, but we'll keep that discussion on the other discussion 😄 ) |
Beta Was this translation helpful? Give feedback.
-
Describe the Bug
Currently importing large amount of data (2 million rows - postcode codes with lat/long) and it's a lot slower when displaying the collection in map view compared to when importing in table view. I guess this is from the map view wanting to update the view regularly (auto refresh is not on)?
So, I'm thinking disable updating the index view whilst importing?
To Reproduce
import a large amount of data via a file when the index view is on map view
Beta Was this translation helpful? Give feedback.
All reactions