This forum deals with any kind of routing computation whether it is simple A:B-routing, calculation of isochrones, simple matrix computation or nearest search.
your routing requests a time consideration mode which has an impact on performance - at least for such a long total distance. So from this point of view I am not surprised.
Your request took me about 2 seconds on TEST and PROD (quite stable on all my 10 calls).
By adding PTV_TruckSpeedPatterns it took roughly 3seconds.
Did you test on a local environment?
Bernd
PS: are the prices you used the final ones? Looks like they are not realistic
<monetaryCostOptions costPerKilometer="10" workingCostPerHour="40" />
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...
We add time consideration mode in request to get toll roads in Czech Republic. Is there another way to get toll roads in Czech Repeblic without time consideration mode? I tested it in an on premise system but i conntected via Internet.
Well, in fact the ExactAt-modes are the most precise ones and require more time than the others.
There's a less time consuming mode called SnapshotTimeConsideration which would return toll prices for countries such as Czech Republic.
I think you have to find the proper balance between quality and performance.
At least I didn't see a fundamental fault in your request.
PS: Do you need all the result field elements that you requested?
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...
OK, so there's improvement, though it is still slower than one would expect.
That's the price for quality
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...