On Friday, April 27, 2018 at 7:12:03 PM UTC+7, JeCh wrote: engine uses only one core of today's standard 8 core CPUs. >
I have no tool to display load of all six cores in real time, but OsmAnd quickly makes my phone extremely hot. No other app (except of benchmark/stress ones) causes comparable heating. So I'm afraid it loads all (or almost all) cores at the same time. rendering is SW only. > Rewriting rendering code from SW to HW is obviously a complex work but SW rendering isn't a global problem. Many applications use SW rendering to display dynamic images with comparable complexity but they don't consume so much CPU power. I think the main problem is very high map detailing. So we need a way to flexibly control map detailing, allowing both easiness for novices and fine-tuning for experts. For experts, there might be individual settings to define POI classes, properties, distance etc., and there might be predefined sets of such settings for novices. The rendering speed could probably be many times faster without loosing > any details if these 2 features will get implemented. > Even it is possible, advanced map detailing control is needed because it is often too hard to have enough details but clear view. With many details, the map becomes unreadable on any scale except very large ones. -- 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.
