I found one thing on the current implementation for the Live map.
To fill the location log (used to draw the map), we use a template sensor to query the location from the vaccum entity. But if you are cleaning big room and if you are cleaning regulary. The history of this template sensor will be hugh (around 60k state value for 10 days). It’s generating useless load on the DB and it can impact the performance. In my case, I had side effect when using the Card creation wizard of HA, the wizard include some card preview based on your existing entity. And unfortutunately it using with hugh entity as example for Histroy graph card and it make the UI freezing …
The fix was to clean the history via SQL (or to way the daily purge) and finally exclude this template sensor from the history and recorder component. There is no impact on the live map and the histroy isn’t generated at all for this device:
I hope it can help people using the Roomba Live map