Skip to content

Commit 60eb135

Browse files
committed
wrong image for pulling study
Signed-off-by: vsoch <[email protected]>
1 parent a91c3fa commit 60eb135

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

_posts/2024/2024-10-04-container-pulling.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -102,11 +102,10 @@ I've been told a few times that moving the containers to be "closer" to the clou
102102
The filesystem has a huge impact in pulling. After all, you are writing and extracting, so having good IOPS must be a variable. And indeed it was! There is a quota for the quantity of SSD per instance family, so I could only go up to a size 64 cluster, but I did see pull times go down a bit.
103103

104104
<div style="padding:20px">
105-
<img src="https://github.com/converged-computing/container-chonks/blob/main/experiments/pulling/analysis/data/run1/img/pull_times_duration_by_size_run1_125_layers.png?raw=true">
105+
<img src="https://github.com/converged-computing/container-chonks/blob/main/experiments/pulling/analysis/data/run3/img/pull_times_duration_by_size_run3_9_layers.png?raw=true">
106106
</div>
107107

108-
109-
We can see that adding a local SSD improves pull times by 1.25x. If you want a simple solution, this storage is pretty cheap so probably worth it. You will need to ask for more quota for larger clusters, however.
108+
We can see that adding a local SSD improves pull times by 1.25x. This particular image is a log of the times, and you can see the full set of images in the [repository](https://github.com/converged-computing/container-chonks/tree/main/experiments/pulling). If you want a simple solution, this storage is pretty cheap so probably worth it. You will need to ask for more quota for larger clusters, however.
110109

111110

112111
### Big daddy SOCI snapshotter!

0 commit comments

Comments
 (0)