4 ms·
Could anyone explain, please, where's the 100x acceleration they mention? The screen records compare 36 seconds to 13 seconds, that's roughly 3x. Also, this pi
by culebron21 8mo ago
Could anyone explain, please, where's the 100x acceleration they mention? The screen records compare 36 seconds to 13 seconds, that's roughly 3x.
Also, this piece:
> 100x speedup is achieved by comparing HH with bidirectional A*. 2-phase A* already uses many heuristics which don't always create an optimal route and still 5-10x slower.
So, 2-phase A* is 5-10x slower than bidirectional A*?
- nicman23 8mo agomaybe cputime shenanigans ie multi core?
- dominicrose 8mo agoThe documentation is also confusing, these labels don't make any sense. Routing type (Android) / Routing algorithm (iOS) - A* 2-phase (Android) / A* (iOS) - A classic* (Android) / Highway hierarchies (iOS) - HH (Highway Hierarchies) x C++ (Android only)
- Aachen 8mo agoThe part you cited explains it. The 100x speedup is achieved by comparing to a method they didn't use anyway because it was too slow, but one that would find an optimal route like HH presumably does—when you have the default profiles and not a custom vehicle speed (like me who doesn't drive 130km/h because it's marginal gains for exponential fuel/CO2 use, so I configured the routing engine to find the best route for a vehicle with max speed 105)