[GraphHopper] Cruiser (mapsforge) and GraphHopper

[Peter K]

Hey,

>> When you try RAM_STORE on Android this probably won't happen.
>
> Actually I see the same behavior even with RAM_STORE.
> The route calculations after the 1st one are more quick and seem to
> getting quicker over the time for the first ones.
> I measured the time also by using your StopWatch method from Android
> sample.

With the dalvik hotspot in mind that is not too strange. Although I
expected the loading from disk a lot more important

>
>> a random query through the area is probably more efficient and simpler.
>
> This approach could work if the random query has valid from / to so
> that the route calculation can finish,
> but with random graphs from the disk how can we get valid from / to
> locations?

e.g. instead of using the lat,lon you can use two random node ids for
querying the algorithm. But this requires using low level API so maybe I
should introduce a graphHopper.warmUp method. Feel free to open an issue
for this or even better a pull request :)

Regards,
Peter.

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