查看: 24|回复: 5

5.6 上下文怎么缩回 258k 了

[复制链接]

1

主题

10

回帖

23

积分

新手上路

积分
23
发表于 2026-7-13 15:50:28 | 显示全部楼层 |阅读模式
记得明明已经提高到 300 多了,然后我感觉最近触发压缩有点快,结果看了下不知道什么时候变回 258k 了?
回复

使用道具 举报

1

主题

8

回帖

19

积分

新手上路

积分
19
发表于 2026-7-13 15:55:16 | 显示全部楼层
大家抱怨 token 消耗太快,又改回去了
回复

使用道具 举报

1

主题

10

回帖

23

积分

新手上路

积分
23
 楼主| 发表于 2026-7-13 15:56:04 | 显示全部楼层
@molvqingtai #1 原来就是这样解决的吗。离谱
回复

使用道具 举报

0

主题

14

回帖

28

积分

新手上路

积分
28
发表于 2026-7-13 15:59:42 | 显示全部楼层
@molvqingtai

笑死
回复

使用道具 举报

1

主题

15

回帖

33

积分

新手上路

积分
33
发表于 2026-7-13 16:02:10 | 显示全部楼层
准确说是 272K ,之前是 372K 。TiBo 原文:- We have landed inference optimizations and are passing down savings to all the subscriptions for GPT-5.6 Sol. That should result in around 10% more usage on its own.
- We noticed that by changing the context size limit in the product to 372k for GPT-5.6 Sol, up from 272k for GPT-5.5, it resulted in more usage being charged than intended. We have reverted to 272k and will work to roll back out to 372k in the days to come. You should notice that usage drains significantly less after this change.
- To understand where the extra usage was coming from, we ran some experiments where reasoning efforts were changed (referred to as juice values under the hood) and have reverted this.
- There is slightly more usage of multi-agent than intended in high and xhigh reasoning effort, we are fixing this going forward. Also fixing a small other thing we noticed with auto-review where we can be more efficient.
回复

使用道具 举报

0

主题

3

回帖

6

积分

新手上路

积分
6
发表于 2026-7-13 16:03:21 | 显示全部楼层
@honjow #2 应该是临时解决,估计哪些地方有 bug
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

Powered by Discuz! X5.0 © 2001-2026 Discuz! Team.

在本版发帖
返回顶部