知识卡片
负载模型要回到真实流量
根据猜测设定扩容阈值,即使压测通过也可能在真实环境崩溃。先观察实际请求率,再以相应并发、资源与响应约束验证,才能定位容量不足还是其他故障。案例120、300、1200请求每秒只是说明测量落差,不能直接用于别的服务。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Putting Evolutionary Architecture into Practice · 查看原书依据
After running the fitness function, the team realized that the average number of calls was 1,200 per second, greatly exceeding their estimate. Thus, the team updated the scaling factor to reflect reality.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第09章《Putting Evolutionary Architecture into Practice》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch09.html;段落定位:After running the fitness function, the team realized)
- 结论依据:原文对“负载模型要回到真实流量”的定义或案例,支撑“根据猜测设定扩容阈值,即使压测通过也可能在真实环境崩溃”的归纳。据其上下文,先观察实际请求率,再以相应并发、资源与响应约束验证,才能定位容量不足还是其他故障。
- 原始内容:After running the fitness function, the team realized that the average number of calls was 1,200 per second, greatly exceeding their estimate. Thus, the team updated the scaling factor to reflect reality.