Every Tuesday at 02:00 UTC, the system logs: “ams cherish i have some 250 further sets install” but then hangs for 45 minutes.
ams deploy --dry-run --sets 250 --module cherish Approve the pending installation: ams cherish i have some 250 further sets install
| Component | Per Set | 250x Total | |-----------|---------|-------------| | RAM (MB) | 128 | 32,000 MB | | Disk (GB) | 2 | 500 GB | | Network (Mbps) | 5 | 1250 Mbps (burst) | Every Tuesday at 02:00 UTC, the system logs:
avg_over_time(ams_cherish_pending_sets[5m]) > 200 Alert when pending sets exceed 250 for more than 10 minutes. The message “ams cherish i have some 250 further sets install” is not an error. It is an acknowledgment of scale . It means your AMS is alive, your Cherish module is functioning, and your infrastructure is capable of handling medium-batch deployments. The question is not if you will see this message, but how efficiently you will act on it. It is an acknowledgment of scale
ams install --sets 250 --source cherish/cache During execution, monitor with:
ams cherish --on-message "i have some 250 further sets install" --execute "ams commit" Add this to your .bashrc or AMS event listener. Background: A Fortune 500 chip manufacturer uses AMS (Adaptive Manufacturing Software) to deploy process control sets to 250 wafer steppers. The internal module “Cherish” manages recipe versioning.