reduce container init time

[RuiFilipeCampos]

• [x] create AMI with base layers already cached
• [x] create AMI with docker pre-installed
• [ ] https://github.com/Digital-Defiance/llm-voice-chat/issues/19 , though fairly low impact in comparison to caching
• [ ] clone repository outside the containers and map volumes to it, low impact

[RuiFilipeCampos]

https://eu-south-1.console.aws.amazon.com/imagebuilder/home?region=eu-south-1#/images/arn:aws:imagebuilder:eu-south-1:572089465582:image%2Fcreate-image%2F1.0.0%2F1/details/workflow

[RuiFilipeCampos]

ami-00e9a577171a99277 - waiting for availability

[RuiFilipeCampos]

2 minute saving only, I'm redoing the AMI so that it caches the images in their entirety

[RuiFilipeCampos]

the final bottleneck seems to be the creation of the containers

cannot optimize unless I change the configuration strategy

will have to stop after this AMI and schedule this task to be done when implementing the next experiment

[RuiFilipeCampos]

ami-0d95b58c016382e64 - waiting for availability

[RuiFilipeCampos]

I think 1m30s of container init is acceptable, there was a redis version mismatch, so those 30s might get cut too

I'm closing this