[GH-ISSUE #9893] Input Latency in Chat Box Due to Autocomplete Suggestion Matching (v0.5.11) #31215

Closed
opened 2026-04-25 05:15:38 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @cr-zhichen on GitHub (Feb 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9893

Installation Method
Docker-compose

Environment

  • Open WebUI Version: v0.5.11
  • OS: macOS 14.6.1 (23G93)
  • Browser: Edge 132.0.2957.140

Expected Behavior
Responsive text input with smooth autocomplete suggestions.

Actual Behavior
Severe input lag when typing/pasting long text (>500 characters) in chat input box.

Bug Analysis
Performance profiling identifies the search() function in the real-time suggestion matching feature as the primary bottleneck:

  1. 70-80% main thread time consumed by search() calls
  2. Linear performance degradation with input length
  3. Frequent function executions per keystroke

Reproduction Steps

  1. Fresh Docker-compose deployment
  2. Open chat interface
  3. Input 1000+ character text
  4. Observe typing latency increasing with text length

Evidence
Performance profile showing search() dominance:
Performance Screenshot

Originally created by @cr-zhichen on GitHub (Feb 13, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/9893 **Installation Method** Docker-compose **Environment** - Open WebUI Version: v0.5.11 - OS: macOS 14.6.1 (23G93) - Browser: Edge 132.0.2957.140 **Expected Behavior** Responsive text input with smooth autocomplete suggestions. **Actual Behavior** Severe input lag when typing/pasting long text (>500 characters) in chat input box. **Bug Analysis** Performance profiling identifies the `search()` function in the real-time suggestion matching feature as the primary bottleneck: 1. 70-80% main thread time consumed by `search()` calls 2. Linear performance degradation with input length 3. Frequent function executions per keystroke **Reproduction Steps** 1. Fresh Docker-compose deployment 2. Open chat interface 3. Input 1000+ character text 4. Observe typing latency increasing with text length **Evidence** Performance profile showing `search()` dominance: ![Performance Screenshot](https://img-cdn.ccrui.cn/2025/02/13/67add9614d011.png)
Author
Owner

@tjbck commented on GitHub (Feb 13, 2025):

You can disable rich text input.

<!-- gh-comment-id:2657677187 --> @tjbck commented on GitHub (Feb 13, 2025): You can disable rich text input.
Author
Owner

@cr-zhichen commented on GitHub (Feb 13, 2025):

You can disable rich text input.

In my OpenWebUI, the rich text input feature has never been enabled. I believe this issue was introduced in version 0.5.10. When typing in the input box of a new conversation, the frontend's matching of prompt suggestions causes a significant performance degradation.

<!-- gh-comment-id:2657919948 --> @cr-zhichen commented on GitHub (Feb 13, 2025): > You can disable rich text input. In my OpenWebUI, the rich text input feature has never been enabled. I believe this issue was introduced in version 0.5.10. When typing in the input box of a new conversation, the frontend's matching of prompt suggestions causes a significant performance degradation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#31215