@GenericT 其实知道会自己锁死自己的。但过度自信，二是为了方便统一管控权限。后面估计涨记性了，毕竟停一天损失上亿

其实知道会自己锁死自己的。但过度自信，二是为了方便统一管控权限。后面估计涨记性了，毕竟停一天损失上亿

同时回滚到旧版本，并重启 API 后台服务，但此时因为承载 API 服务的容器平台也依赖 API 服务才能提供调度能力，即发生了循环依赖。

这是哪个脑残设计的自己把自己锁死在房间里的架构？

@liyafe1997 怪不得 win+g 显示的利用率和任务管理器不一样

@liyafe1997 如果是这样任务管理器这个利用率等于废了。
利用率应该按总硬件可用资源来算，他这个算法根本就不知道自己 CPU 资源空闲情况，纯属智障设计。

C:\Users\louis>typeperf "\Processor(_Total)\% Processor Time"

"(PDH-CSV 4.0)","\\PC\Processor(_Total)\% Processor Time"
"03/09/2024 02:29:34.869","5.851351"
"03/09/2024 02:29:35.881","6.604089"
"03/09/2024 02:29:36.896","4.567412"
"03/09/2024 02:29:37.903","6.080964"
"03/09/2024 02:29:38.907","6.676061"
"03/09/2024 02:29:39.921","5.739719"
"03/09/2024 02:29:40.933","6.061616"
"03/09/2024 02:29:41.946","7.105614"
"03/09/2024 02:29:42.949","5.405625"
"03/09/2024 02:29:43.961","6.507713"
"03/09/2024 02:29:44.975","6.220408"
"03/09/2024 02:29:45.983","5.104340"
"03/09/2024 02:29:46.991","6.976620"
"03/09/2024 02:29:47.999","5.779769"
"03/09/2024 02:29:49.014","6.003389"
"03/09/2024 02:29:50.023","5.642427"
"03/09/2024 02:29:51.030","4.195449"
"03/09/2024 02:29:52.046","7.199734"
"03/09/2024 02:29:53.053","6.338479"
"03/09/2024 02:29:54.071","6.368493"
"03/09/2024 02:29:55.077","5.696843"
"03/09/2024 02:29:56.084","7.372224"
"03/09/2024 02:29:57.087","6.669164"
"03/09/2024 02:29:58.092","5.040269"
"03/09/2024 02:29:59.106","7.432648"

@yuanmomo 是的，正常修改一个模块是要触发整体构。

@google2020 国有公司里面各省市书记可不像私营分公司的 CEO 说开就能开的。