You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was doing some profiling and found that lower layers prefetches take more time to start than the previous layer prefetch. I would like to know if this the expected behavior and why? (I thought all prefetches are started simultaneously)
By prefetch start, I mean the time layer.Prefetch is invoked (calculated using time.Now().UnixNano()):
The image I tested was drupal_latest: https://hub.docker.com/_/drupal, although this behavior was exhibited for every image I tested. (Image was optimized to eStargz with gzip compression level 9)
This is because the prefetch of each layer is called after verification which is not performed simultaneously.
I've created a patch #467 to fix this issue.
Hello,
I was doing some profiling and found that lower layers prefetches take more time to start than the previous layer prefetch. I would like to know if this the expected behavior and why? (I thought all prefetches are started simultaneously)
By prefetch start, I mean the time
layer.Prefetch
is invoked (calculated usingtime.Now().UnixNano()
):stargz-snapshotter/fs/layer/layer.go
Line 439 in 25d16aa
The image I tested was
drupal_latest
:https://hub.docker.com/_/drupal
, although this behavior was exhibited for every image I tested. (Image was optimized to eStargz with gzip compression level 9)stargz-snapshotter commit id: 94f9987
/etc/containerd-stargz-grpc/config.toml:
The total time to prefetch all layers was 1.49686s
Would love some clarity on this. Thank you.
The text was updated successfully, but these errors were encountered: