Long response time for no path found if end too far away from graph

[azarz]

Bug

Describe the bug

If the start or end point is too far away from the graph, sometimes no path is found by road2. This is OK, however the response time for the error to return.

Type of use (choose between):

• service provided by Road2 (ex. bug with a request from the API simple/1.0.0)

Type of bug (choose between):

• request, for bugs with an API

To Reproduce

Steps to reproduce the behavior:

1. On the server deployed on Géoplateforme, make the following request:
   https://data.geopf.fr/navigation/itineraire?resource=bdtopo-pgr&start=4.8292148%2C48.845765&end=49.996981%2C48.845765
2. The response time is too long, even with the OSRM resource. Here are curl timings:

time curl -sS "https://data.geopf.fr/navigation/itineraire?resource=bdtopo-pgr&start=4.8292148%2C48.845765&end=49.996981%2C48.845765"
{"error":{"message":" No path found "}}
real	0m40,646s
user	0m0,037s
sys	0m0,010s

time curl -sS "https://data.geopf.fr/navigation/itineraire?resource=bdtopo-osrm&start=4.8292148%2C48.845765&end=49.996981%2C48.845765"
{"error":{"message":" No path found "}}
real	0m2,212s
user	0m0,043s
sys	0m0,004s

Expected behavior

The not path found error should return faster

Environment (please complete the following information):

• road2 server on the Géoplateforme

Data:

Type of data: osrm, pgrouting
Generation of the data: pgrounting: using Géoplateforme's warehouse API. OSRM: using r2gg on a VM owend by IGNF.