Reduce routing time calculation by scripts and tile management.

[MJokar67]

Given the following repository link and terminal command:
Alpimaps valhalla route package

Create routing package command:
python ./scripts/build_valhalla_package.py --id $AREA --poly $AREA.poly --polymaxzoom=11 valhalla_tiles ${OUTPUT_DIR}/${AREA}/${AREA}.vtiles

What is the effect of changing --tilemask? There is also a tile_mask=10 hardcoded in the scripts.
What is the effect of changing --polymaxzoom=14 instead of 11?

I want to increase the speed of route calculation and file size is not my concern.

I have generated Iran and Russia map packages separately with --polymaxzoom=11
The route calculation performance of the Iran map is about 3 seconds in the worst case.
But for the Russia map with two route points 500 meters apart, the calculation time takes 3 seconds in the best case.

How can route calculation time be improved?

[farfromrefug]

@MJokar67 poly max zoom is used to generate the ost of tiles to generate.
So it won't change anything on computation time, only mbtiles size.

Computation time mostly depends on data and Valhalla version.
The more complex the network of roads is in an area the longer it will take to compute.
You might try to play with Valhalla compute options. This could.make LA difference

[MJokar67]

In my experience, there is a direct relationship between the number of tiles, the depth of the tiles subdivision, the amount of data that can be searched in a tile, and performance. You mentioned the size of the .mbtiles, but I tried both poly zoom 10 and poly zoom .14 and the difference in file size is only a few kilobytes.

I've compiled the latest valhalla and generate tiles separately.

.What do you mean by compute option?

[farfromrefug]

@MJokar67 number of tiles will only matter really if your route can go through many tiles. If not then it wont matter. Compute options are the options you pass to Valhalla API through carto API. Like use_road or others.