Impact of number of loading patterns on performance
Posted: Thu Oct 27, 2022 9:04 am
Hi DEV,
one of my partners wants to deal with loading patterns in xTour2, e.g. 34 different patterns
[0] --> 33 palettes, zero Dingelhopper
[1] --> 32 palettes, 2 Dingelhoppers
[2] --> 31 palettes, 4 Dingelhoppers
..
[32] --> 1 palette, 64 Dingelhoppers
[33] --> 0 palettes, 66 Dingelhoppers
I am aware of the meachnism and just curious: what is the impact of a bigger number of vehicle loading patterns on
edit 27.10.2022: we regularly try to improve our performance - maybe the statement above is subject to change once we put that specific challenge on our desk.
Bernd
one of my partners wants to deal with loading patterns in xTour2, e.g. 34 different patterns
[0] --> 33 palettes, zero Dingelhopper
[1] --> 32 palettes, 2 Dingelhoppers
[2] --> 31 palettes, 4 Dingelhoppers
..
[32] --> 1 palette, 64 Dingelhoppers
[33] --> 0 palettes, 66 Dingelhoppers
I am aware of the meachnism and just curious: what is the impact of a bigger number of vehicle loading patterns on
- performance
- quality
- If this value is set to BetweenTrips the algo has to iterate over a compareably huger number of combinations. In some tests with about 100 patterns this caused a performance decrease of 2.5.
- If this value is set to AtStop we can interrupt once we found a first valid pattern. (Worst case: if the last existing pattern is "the first valid one" we also have to iterate over 100%)
edit 27.10.2022: we regularly try to improve our performance - maybe the statement above is subject to change once we put that specific challenge on our desk.
Bernd