Daily registry updates

Your model registry is stored in your Modelbit Git repo. Every call to mb.add_models creates a new commit on that branch. Storing model changes with commits makes it easy to test new models on branches and make model changes part of pull requests.

However, if you automatically retrain thousands of models per day you'll end up with a very long Git history full low-value commits. These long histories can interfere with pull request workflows or make reading Git histories challenging.

To avoid this issue, Modelbit can automatically queue model updates throughout the day and store them all in a single Git commit. With this setting enabled, you'll only have one Git commit per-day related to model updates regardless of how many models were updated.

Enable daily updates

In Modelbit, go to Settings then Git Settings. Find the branch you want to use with daily registry updates and click "Registry settings" button.

Then specify when you want the daily updates saved to Git. Every day, all pending model updates will get saved to Git at that time. Turning off daily updates will immediately save any pending updates to Git.

Pending model changes are not available to running deployments. Models are only available to deployments after they are saved to Git. That means any models you've added/deleted/changed throughout the day will only be visible to calls like mb.get_model after the daily update saves them to Git.