We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
例行检查
问题描述
通过one-api与直接链接原服务API的FIM的token情况,通过one-api的FIM的token消耗大约是直连的5~10倍
复现步骤
比较两个类似场景(vscode continue, 相同workspace,打开相同的一些文件,对同一个文件从0开始编辑类似的内容), one-api 比直连的 token 消耗及费用都要高,用两个不同的api key,可以在服务商网站上看到one-api出去的,token消耗量要10倍左右
从one-api的日志看,似乎"补全"的token异常高,经常维持在4k左右
相关截图
The text was updated successfully, but these errors were encountered:
No branches or pull requests
例行检查
问题描述
通过one-api与直接链接原服务API的FIM的token情况,通过one-api的FIM的token消耗大约是直连的5~10倍
复现步骤
比较两个类似场景(vscode continue, 相同workspace,打开相同的一些文件,对同一个文件从0开始编辑类似的内容), one-api 比直连的 token 消耗及费用都要高,用两个不同的api key,可以在服务商网站上看到one-api出去的,token消耗量要10倍左右
从one-api的日志看,似乎"补全"的token异常高,经常维持在4k左右
相关截图
The text was updated successfully, but these errors were encountered: