Why needs the new map more CPU activity ( or is my laptop at fault ) ?
I'm using Windows 10 and FireFox & Chrome, all newest versions/updates. For a test, I have in FireFox 3 tabs open, one with nothing ( empty ), one with the old map and in the last tab the new map. When showing the empty tab, the cpu is steady +/- 2% ( I have all other windows closed, except Task-Manager ). After switching ( just a mouse click ) to the old map, the cpu ( & wifi ) 'jumps' up a bit, but both slow down after a few seconds. When switching to the last tab ( with the new map ), the cpu goes to +/- 20% and stays there. When switching back to the empty FireFox tab, the cpu goes down to +/- 2% again
The same thing happens in Chrome, but the max. cpu load is lower ( 2% to a steady 8%, in the new map ).
Of course there are more Windows processes active, but these stay the same when switching between tabs. Adding the same cpu percentage to the cpu-total for each tab. So the difference between the old and the new map, is in FireFox about ( 20 - 2 = ) 18% more cpu load.
Oké, the data in the new map needs to be loaded and displayed on the screen, but after that, there's nothing to be computed. The map is static, because you need to click on "Search this area" to reload caches and displaying them, so there's nothing to do for the cpu. So why the high cpu-load?
When using a laptop or desktop, this ( higher cpu level ) is not a big problem. But why is there such a difference between the old and new map and what happens when using a mobile phone or tablet? A higher cpu load, is a bigger load on the battery.
See small Wi-Fi activity window for when switching between tabs.