infiniflow / infiniflow/ragflow

[Bug]: Why the multi-turn optimization always spend time although I turn off it?

Open
#7,705 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

🐞 bug
Dominant language
Go
Stars
91k
Forks
10.8k
Avg merge
1d 14h
Merged PRs (30d)
705

Description

### Self Checks

- [x] I have searched for existing issues [search for existing issues](https://github.com/infiniflow/ragflow/issues), including closed ones.
- [x] I confirm that I am using English to submit this report ([Language Policy](https://github.com/infiniflow/ragflow/issues/5910)).
- [x] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) ([Language Policy](https://github.com/infiniflow/ragflow/issues/5910)).
- [x] Please do not modify this template :) and fill in all the required fields.

### RAGFlow workspace code commit ID

#6854

### RAGFlow image version

nightly

### Other environment information

```Markdown

```

### Actual behavior

![Image](https://github.com/user-attachments/assets/3dfb1441-95e2-4cf0-a77d-51dafe5b6fd7)

![Image](https://github.com/user-attachments/assets/1cca458a-00b5-40c4-abc1-b4c238a491e1)

### Expected behavior

_No response_

### Steps to reproduce

```Markdown
chat and find it apparently much slower than retrieval test
```

### Additional information

_No response_

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. First reproduce the slowdown in chat versus the retrieval test with multi-turn optimization disabled, then trace where that setting is read and where the optimization work is invoked. Done means disabled optimization no longer adds the reported delay, with a regression check for both enabled and disabled behavior.

Written by the indexing model from the issue text.

Assessment

Domain
ai
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.