instance pdp v obj run time (s)
VLSN iVLSN VLSN iVLSN ratio VLSN iVLSN ratio
LC1 2 1 106 21 21 2751,02 2846,57 1,03 4,03 3,37 0,83
LC1 2 2 105 21 21 3073,23 2957,60 0,96 6,73 4,75 0,71
LC1 2 3 103 19 19 2843,31 2916,15 1,03 11,98 7,23 0,60
LC1 2 4 105 20 20 2899,35 2865,18 0,99 27,61 14,64 0,53
LC1 4 1 211 42 41 7495,28 7293,53 0,97 16,46 10,56 0,64
LC1 4 2 211 42 41 7560,14 7522,12 0,99 34,66 18,99 0,55
LC1 4 3 210 40 39 7693,29 7597,88 0,99 71,49 35,35 0,49
LC1 4 4 208 39 38 7472,94 7439,01 1,00 149,93 61,09 0,41
LC1 8 1 420 83 82 26348,18 25700,49 0,98 80,74 43,07 0,53
LC1 8 2 423 84 81 26631,66 26051,93 0,98 168,09 81,18 0,48
LC1 8 3 417 80 78 27296,86 26929,49 0,99 289,46 119,73 0,41
LC1 8 4 416 73 71 25308,23 25183,71 1,00 690,71 224,44 0,32
LC1 10 1 527 103 101 43639,52 42981,64 0,98 157,25 83,16 0,53
LC1 10 2 523 103 100 45872,24 44753,14 0,98 307,36 145,21 0,47
LC1 10 3 524 98 95 44909,41 44286,61 0,99 631,19 248,87 0,39
LC1 10 4 519 92 86 42564,03 41187,36 0,97 1332,51 430,09 0,32
Figure 4: Comparing VLSN and iVLSN.
5 BENCHMARKS
This section presents the benchmarks of our VLSN
approach on standard PDP problems (Lim, 2008),
with and without gradual enrichment, and compares
them to the best known values. We selected a set of
instances of various sizes. Each benchmark is run 13
times with the standard VLSN algorithm and 13 times
with the iVLSN algorithm.
The official benchmarks are about: first, minimiz-
ing the number of vehicles, and second, minimizing
the total distance. VLSN is not meant to minimize
the number of vehicles, so this is not a relevant di-
mension. Yet, we report these numbers as well for the
sake of completeness.
Figure 4 presents a comparison of the VLSN and
iVLSN algorithms on the selected benchmarks. As al-
ready mentioned, these approaches are not about min-
imizing v, so the related columns are not relevant but
mentioned for completeness. obj reports the median
value for the objective function over the 13 runs with
the ratio and run time reports the median run time for
the algorithms, in seconds with the ratio. We observe
two things: (1) the run time is improved by the in-
cremental approach, as initially intended. However,
the run time ratio does not seem to be strongly related
to v or pdp. iVLSN achieves a speedup factor of 3
in the best case. (2) there is a slight improvement in
quality of the solution in iVLSN, which was not a pri-
mary goal of this algorithm. We conclude that iVLSN
seems to be a relevant improvement over VLSN when
applied on PDPTW problems.
The benchmarks have been run on a Dell lap-
top featuring Windows 10, an INTEL
R
core
TM
i7
with 4 physical cores (thus 8 logical cores) running
at 2.2GHz and 16Gb of RAM. The benchmarks were
performed in a single thread.
Figure 5 compares VLSN and iVLSN against the
best values for the selected benchmarks, fetched from
(Lim, 2008) in September 2020. We observe that
VLSN and iVLSN do not reach the quality of the best-
known solution.
We compare the inner behaviour of VLSN and
iVLSN on a single run of the algorithms on the
LC1 2 4 problem instance in Figure 6. At each itera-
tion of the algorithm, it reports for both algorithms (1)
the number of edges in the VLSN graph and (2) num-
ber of such edges that were fetched from the cache
and (3) the number of edges that were explored. In
this problem instance, VLSN and iVLSN took nearly
the same number of iterations: 34 and 39, respec-
tively.
At any time, iVLSN explores fewer edges than
VLSN. In total, iVLSN explores 43% of the edges
explored by VLSN. The total run time of iVLSN is
53% of the time taken by VLSN. The gain in time is
not as high as the gain in number of edges because
the iVLSN executes the cycle detection algorithm per
iteration and performs a few more iterations in this
case.
After a start-up phase, where the VLSN injects
many pick-up-delivery pairs into the route, the total
number of edges explored by the VLSN decreases
throughout the search because the cache is more and
more effective. The iVLSN has the opposite be-
haviour; it explores more and more edges throughout
ICORES 2021 - 10th International Conference on Operations Research and Enterprise Systems
278