[GraphHopper] Cruiser (mapsforge) and GraphHopper

[Peter K]

> Is there some kind of initialization which delays the 1st route
calculation,
> which we can call asynchronously with the graph read, so that the
route calculations can perform equally fast?

When you try RAM_STORE on Android this probably won't happen. So yes,
the default memory mapped config is more efficient when data is loaded
(partially) from disk into memory. A trick could be to call
mappedBuffer.load for all segments in the MMapDataAccess object, but a
random query through the area is probably more efficient and simpler.

Regards,
Peter.

> Hi Peter,
>
> At Android after the application start, the 1st GH route calculation
> is notably slower than the next ones, which perform faster.
> This is serious for the first time user experience (I have received
> reports about this).
>
> Is there some kind of initialization which delays the 1st route
> calculation, which we can call asynchronously with the graph read, so
> that the route calculations can perform equally fast?
>
> -- 
> Emux
> Cruiser <http://wiki.openstreetmap.org/wiki/Cruiser> - Atlas
> <http://wiki.openstreetmap.org/wiki/Atlas_%28navigation_application%29>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20140501/c4b5a304/attachment.html>