Java has come a long way. Java is one-time compiled and then almost as fast as C/C++. Java already supports multicore processors for years and also the OsmAndMapCreator can be started with the number of cores to use (or via the config) Note also that for the bigger maps, the disk access is way more important than the difference in speed for C/C++ or java. Using lots of memoriesand superfast solid state disks gives you the best performance by whole factors. And yes: switching to C++ might get you the last few percentages.
Harry Op vr 5 jul. 2019 om 10:50 schreef Helmut Jarausch <[email protected]>: > Are there any ongoing efforts to rewrite the software to create the maps > in C++? > I would expect a significant speedup on multicore processors. > > 'Xavier' via Osmand <[email protected]> schrieb am Do., 4. Juli > 2019, 20:56: > >> On Thu, Jul 04, 2019 at 02:14:21PM -0400, Greg Troxel wrote: >> > >> >I also don't understand why people are so upset about monthly updates >> >being 10-20 days behind the end of the month. Yes, the next day would >> >be better, but 1) it's so much faster than any non-OSM approach >> >> If I remember correctly, back when I had a TomTom, the map updates from >> TomTom were available either on a 6 month cycle or yearly cycle. >> >> OsmAnd monthly updates, even if they don't arrive until the 10th of the >> month, are already either six or twelve times more frequent than what >> TomTom provided. >> >> I don't know what cycle TomTom is on now, as I switched to OsmAnd when >> TomTom decided to drop support for my old navigator. >> >> > and 2) with osmand live, it matters very little. Even without >> >osmandlive, having map data that's between 20 and 50 days old at any >> >point isn't much worse than having data that's between 5 and 35. >> >> 20-50 days old seems better than 180 or 365 days old (and of course >> with TomTom one had to pay per update or 'subscribe' to a limited >> number of updates). >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/osmand/20190704185647.GN1375%40d820.dp100.com >> . >> 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/osmand/CA%2BCgGZRsKdoZwQrBth1okp1WxXsD4bqnTrDk72X5CUXQvXbmCQ%40mail.gmail.com > <https://groups.google.com/d/msgid/osmand/CA%2BCgGZRsKdoZwQrBth1okp1WxXsD4bqnTrDk72X5CUXQvXbmCQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPptreZ53N58bwMsR%3DEwDUtRgVoz%2BxiD%2BiE53inPBMkiMwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
