-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Spike/R&D] Cache usage in tutor-mfe build #210
Comments
My final insights after running everything: First-time build or --no-cache build:
Second time build
Answers to the Questions:
How npm install work?
If anyone else want to add something, feel free to share. If anyone else wants to add something, feel free to share. |
Docker cache is shared properly across layers. Regarding npm cache, I tried building the images with the |
Updates: With |
This is a great writeup. Thank you all! |
@tasawar-hussain suggested three ways to consider the cache usage for MFE build:
|
We have good enough context on this, closing this for now. |
In Tutor Users meeting on May 20th, 2024, a large chunk of the meeting was focused on discussing the large build times of tutor-mfe (https://openedx.atlassian.net/wiki/spaces/COMM/pages/3583016961/Tutor+Users+Group#2024-05-20). When various MFEs are building in parallel, both install and build steps take quite a while, often leading to npm connection error. The only workaround is to limit buildx parallelism to 1/2/4, depending on the resources.
One of the items discussed in the meeting was the usage of cache during MFE build. There are various items we would want to test/verify:
tutor-mfe/tutormfe/templates/mfe/build/mfe/Dockerfile
Line 46 in 5bb43fa
-d --progress=plain
in image build command to see expanded logsBesides the above items' verification, identify what cache led (or other workarounds) can we do to improve/reduce MFE build times.
The text was updated successfully, but these errors were encountered: