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
Multistage builds help separate heavier development dependencies from lighter production dependencies without compromising on all the things that make containers nice.
The classic example is separating compilation from deployment. If training is model compilation, why not borrow this best practice?
Less ambitiously, it might be possible to use them for splitting frontend/backend(s). Right now, we've got gradio and pandas in our Lambda, which is costing us whole seconds each inference.
The text was updated successfully, but these errors were encountered:
Multistage builds help separate heavier development dependencies from lighter production dependencies without compromising on all the things that make containers nice.
The classic example is separating compilation from deployment. If training is model compilation, why not borrow this best practice?
Less ambitiously, it might be possible to use them for splitting frontend/backend(s). Right now, we've got gradio and pandas in our Lambda, which is costing us whole seconds each inference.
The text was updated successfully, but these errors were encountered: