Description
Stacking the same assets - once with reading from a local directory, the other time with reading from the original remote source - shows different performances. Stacking local elements takes more time on average.
Expected behaviour
Stacking assets that are available locally (on a fast SSD storage close to the CPU unit) should be faster than stacking remote assets, which need to be fetched via low bandwidths first.
Investigation/Reproduction
So far I have only been able to narrow down the phenomenon to the extent that it seems not related to the actual I/O, insofar as the time difference between stacking local and remote assets also persists when using the FakeReader. The time difference in the example below is as follows:
Description Stacking the same assets - once with reading from a local directory, the other time with reading from the original remote source - shows different performances. Stacking local elements takes more time on average.
Expected behaviour Stacking assets that are available locally (on a fast SSD storage close to the CPU unit) should be faster than stacking remote assets, which need to be fetched via low bandwidths first.
Investigation/Reproduction So far I have only been able to narrow down the phenomenon to the extent that it seems not related to the actual I/O, insofar as the time difference between stacking local and remote assets also persists when using the
FakeReader
. The time difference in the example below is as follows: