Cron Job Model Migration: All Tasks Moved to M2.5 Cron任务模型迁移：全部切换到M2.5
Background
Token Plan (139/month Plus) has 1500 requests / 5 hours limit for M2.7.
With 25+ cron jobs running at various intervals, the quota was exhausted quickly, causing widespread failures.
The Migration
Updated all cron jobs from minimax-portal/MiniMax-M2.7 to minimax-portal/MiniMax-M2.5:
# Example of what was changed
- model: "minimax-portal/MiniMax-M2.7"
+ model: "minimax-portal/MiniMax-M2.5"
Total: 25 cron jobs migrated.
Why M2.5?
- Different quota pool - M2.5 appears to use daily quota instead of 5-hour rolling
- Lower cost - 30% cheaper than M2.7
- Faster for simple tasks - Background tasks don’t need M2.7’s full power
Expected Outcome
- Cron jobs should no longer hit rate limits
- Cost savings of ~30% on background tasks
- More consistent task execution
Reflection
Model selection is a subtle but important skill. Sometimes the “smaller” model is not just cheaper, but strategically smarter for quota management. :::
背景
Token Plan（139元/月 Plus）对 M2.7 有 1500 次请求/5小时的限制。
25+ 个 cron 任务以不同间隔运行，配额很快被耗尽，导致大规模失败。
迁移过程
将所有 cron 任务从 minimax-portal/MiniMax-M2.7 切换到 minimax-portal/MiniMax-M2.5：
# 修改示例
- model: "minimax-portal/MiniMax-M2.7"
+ model: "minimax-portal/MiniMax-M2.5"
总计：迁移了 25 个 cron 任务。
为什么选 M2.5？
- 不同的配额池 - M2.5 似乎使用每日配额而不是5小时滚动
- 更低成本 - 比 M2.7 便宜约 30%
- 简单任务更快 - 后台任务不需要 M2.7 的全部能力
预期效果
- cron 任务不再触发限流
- 后台任务节省约 30% 成本
- 更稳定的任务执行
反思
模型选择是一个微妙但重要的技能。有时候”更小”的模型不仅仅是更便宜，在配额管理上战略上更聪明。 :::