聊天历史由 MongoDB 中获取 #113
Merged
聊天历史由 MongoDB 中获取 #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
同时关掉 api 依赖库中的缓存
zhujunsan
commented
May 7, 2023
| @@ -45,6 +46,8 @@ export async function initApi() { | |||
| apiKey: config.apiKey, | |||
| completionParams: { model }, | |||
| debug: !config.apiDisableDebug, | |||
| messageStore: undefined, | |||
zhujunsan
commented
May 7, 2023
| @@ -45,6 +46,8 @@ export async function initApi() { | |||
| apiKey: config.apiKey, | |||
| completionParams: { model }, | |||
| debug: !config.apiDisableDebug, | |||
| messageStore: undefined, | |||
| getMessageById, | |||
|
试了下 很不错，accessToken 应该是官网自带维护的，只需要对应的对话等id， 但是有 2 个小问题，目前会重复1次，以及 另外 我数了下 现在只能回溯前面20条消息（x2=40 重复了1次)，这个数字能否控制更改
|
|
1 重复一次是因为一次是取completion，一次是取prompt，所以我说做一层小缓存是可以在取completion的时候缓存下，再往上取prompt的时候可以不走MongoDB，但要考虑自动失效什么的也挺烦先就没搞了 2 往上追溯多少这个是上游api决定的，这里控制，他往上追溯到上下文大于 model总token数 - 最大completion token数的时候就不加了，默认model 4000，最大completion 1000，所以下一条上下文加上时超过3000token的时候就不加了 |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
重启服务后上下文在提问中得以保存
同时关掉 api 依赖库中的缓存以减少长时间使用后的内存占用
可能带来的问题是上下文条数很多时多次读取 MongoDB 数据库，会加大数据库压力和增大延迟，可以做的优化是做一层小缓存
只试过 API 走 GPT 3.5，accessToken 方式需要测试