does the airgap image autoload feature have differ...
# k3s
a
does the airgap image autoload feature have different loading mechanism than the image load via k3s restart? airgap images via autoload took me 10s while loading via k3s restart took like 1.8s. it was a 61mb file
c
Nope, exact same code is used for both. The whole thing is primarily IO bound.
a
yeaa i see variation in the performance. i just moved this folder out and in again and it imported the images in under 2 secs
other times it spikes up to 6-10s
c
Really just depends on what else your node is doing at the same time
a
our workflow kicks in the helm upgrade while the autoload is happening. prolly thatswhy 🙂
thanks btw