For me this is exactly the reason why I don't use OsmAnd anymore for car navigation: rendering is way too slow! I'm still very enthusiastic using it in cycling and hiking, where rendering can be much slower due to the lower speeds and therefore lower map/screen refresh rate.
It has been confirmed by Victor already a couple of times in the past, and it is one of the improvements we are all waiting for. One of the reasons is also that OsmAnd is single-threaded. I have a quad-core android head-unit in my car and an 8-core relatively fast phone, but if OsmAnd is only using one core there is not much use of quad-core or 8-core. Note that it is also part due to the fact that OsmAnd has really by far the most detailed maps, containing the most map "items" of all nav apps. These huge amount of detailed "items" take some time to render as well. If you use a roads-only map for driving, rendering is much faster (factor 1,5-3. I tested that many times with debug frame refresh info). But I don't like switching back and forth between full and roads-only maps, and having a double set of maps. Roads only maps contain roads, some large map"scenery" polygons (woods, large lakes, big fields, etc), addresses and POIs. Finally: OsmAnd maps are uncompressed binary files, also containing 3 layers of details for the different map zoom levels. With regard to compressed/uncompressed: Having small, fast to read compressed files and using multi-threading to decompress and interpret maps, like some other apps are doing, might also give a performance benefit. Having only one full layer and make the software decide what to show during which zoom-level might give a performance enhancement as well. Note that the 2 low zoom level sections are much smaller, even together, than the full detail high-zoom section, but still not necessary if you ask me. Harry 2017-12-19 2:01 GMT+01:00 Majka <[email protected]>: > The rendering speed is ... slow-ish, but usually usable for me. > > Few tips: > > Check that Mapillary is switched off - this part can block rendering > completely. THIS is a bug, IMHO. > > Use map overlay / underlay / height data only when needed. > > Install only maps you really need and archive what you don't need - you > can "unarchive" easily. > > Do not use road map and detailed map for the same area - for example road > map of Germany and detailed map of Bavaria for driving in Bavaria - Osmand > should render only one of the maps (the selected one), but will try to > search in all of them. An exception would be a very long distance drive, > where the better speed through having only a road map for most of the > distance would be preferable to slower speed caused by the much bigger maps > with details. > > All this will slow the rendering unnecessarily. > > I suspect one problem is that the map is so detailed - there is simply > more data to sift through and to discard when not needed at the moment. > Other apps use much smaller part of OSM data, Osmand has probably the > complete set. > It is a trade-off - slower but detailed map or faster map without all the > additional usability. > > The rendering could be faster, but I can live with the current speed. > > -- > You received this message because you are subscribed to the Google Groups > "Osmand" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
