Running Gradient in Production

Many companies run their data workloads in their production environment in a variety of ways. While there are many ways users can run Gradient in production with the versatile Sync-CLI, below are a few paths that have resonated with users:

If the use cases below don't quite match your use case, please feel free to reach out and we'd be happy to help find a solution. Either contact us via the intercom app or email us at [e-mail]

1. Production auto-enabled - Allow Gradient to continuously monitor, control, and optimize your production jobs.

   • Ideal for - Users who want to optimize many jobs at scale and are comfortable with variations in cost/runtime during training.

2. Optimization Windows - Optimize your production jobs during regularly scheduled maintenance windows, allowing Gradient to control your jobs during a finite period so users can monitor and approve the changes.

   • Ideal for - Users who want more control and oversight over changes that Gradient is making. Typically these jobs may be more sensitive to cost and runtime variations.

3. Development Clones - Allow Gradient to optimize jobs on a clone of your production jobs in a non-production environment. Optimized cluster configurations can then be transferred over to your production jobs.

   • Ideal for - Users who cannot experiment with configurations in production at all and need new configurations to be fully vetted before deploying to production. Typically these are the most conservative users in regards to their production jobs.