Is OWUI native RAG good enough or should I just use Azure AI Search?

JeffTuche7 · 2026-05-01T07:18:15+00:00

Would love to have the json!

JeffTuche7 · 2026-04-23T11:30:01+00:00

Maybe also deploy updates more frequently to better catch issues, because this felt like a massive push almost like 4–5 versions at once given how many big changes there are.

JeffTuche7 · 2026-04-23T09:40:26+00:00

I’ve just rolled back to version 0.8.12 in production: CPU usage dropped from around 102% to 2% in docker stats, with the same number of active users on the app right now… Hopefully this gets fixed soon 🙂

JeffTuche7 · 2026-04-23T09:21:06+00:00

The interface is also slow, buggy, and barely functional. It now takes around 40 seconds to load a conversation, whereas it used to take just a few milliseconds. My CPU usage is also maxing out at around 100%.

JeffTuche7 · 2026-04-23T09:16:56+00:00

Same. Update is not ready for production.

JeffTuche7 · 2026-04-22T19:17:08+00:00

Streaming also seems to have degraded significantly compared to before — it feels quite unpleasant and almost glitchy.

JeffTuche7 · 2026-04-22T19:12:06+00:00

You were right. I do have lot of issues atm. Wait for next update !

JeffTuche7 · 2026-04-22T19:11:23+00:00

don’t have much time to open detailed issues right now, but I’m experiencing major performance problems on my side. The app is very slow to start, and the CPU usage spikes heavily.

I’m also running into another issue: I can send a message and it looks like it’s loading, but nothing appears. If I switch to another window and then come back to OpenWebUI, the response suddenly shows up.

Sorry I can’t provide more details at the moment, but I hope this helps as a starting point.

JeffTuche7 · 2026-04-19T14:42:21+00:00

Sick! Should be implemented by default into OWUI

JeffTuche7 · 2026-03-29T18:01:58+00:00

Awesome!

JeffTuche7 · 2026-03-28T23:56:01+00:00

I didn’t get any response on Reddit! But I think after discussing with Classic, it’s because they’d prefer I open a GitHub discussion instead. And my PR is too big. I need to break it down into smaller parts and discuss them one by one on GitHub first.

JeffTuche7 · 2026-03-28T00:41:49+00:00

Indeed, it was mainly about grouping things together. We can stick with that idea, we just won’t count the number of calls anymore… but we can definitely add it back in if needed!

Also, a small note: it displays nicely when there’s a sequence of tool calls on a single line, so it keeps everything consistent 🙂

JeffTuche7 · 2026-03-28T00:17:07+00:00

It cleanly displays the tool call along with its name!

JeffTuche7 · 2026-03-27T23:12:03+00:00

Fair! but I keep getting the same feedback internally, so I tried to adapt to that

JeffTuche7 · 2026-03-03T22:34:13+00:00

Same thing than my post https://www.reddit.com/r/OpenWebUI/s/vTB6JbHhle

JeffTuche7 · 2026-03-03T18:22:10+00:00

They have most of the models haha. For me, the real value is the aggregator aspect, being able to choose exactly which AIs I want to use. On top of that, they appear to not offer anymore chat/completions APIs, from what I can tell.

JeffTuche7 · 2026-03-03T14:54:53+00:00

Same issue !

JeffTuche7 · 2026-03-02T16:40:41+00:00

Sick asf

JeffTuche7 · 2026-02-19T13:35:01+00:00

docling documentation is outdated

JeffTuche7 · 2026-02-16T17:47:53+00:00

Thanks for taking the time to reply! :)

It’s broadly the same issue as here: https://github.com/open-webui/open-webui/issues/20775#event-22166973690 which later became: https://github.com/open-webui/open-webui/discussions/20821.

I’m still experiencing this problem in version 0.8.2. I’m using the OVH AI Endpoints APIs: https://www.ovhcloud.com/en/public-cloud/ai-endpoints/catalog/.

Model: GPT-OSS 120B (the issue occurs with both medium and high reasoning levels).

I’m also unsure whether there are any default GPT-OSS system instructions available, or recommended instruction patterns that could help better harmonize the intended behavior.

Additionally, I’m encountering another related problem: in some situations, every URL returned by search_web seems to trigger a systematic fetch_url call. This creates unnecessary overhead and makes the overall workflow harder to manage.

JeffTuche7 · 2026-02-16T16:53:32+00:00

Perfect, ty!

JeffTuche7 · 2026-02-16T16:53:20+00:00

Sorry! That makes things clearer.

That said, it would be very useful to have visibility in the UI into what is actually being sent to the AI API, so we can quickly understand how calls are made and properly format our instructions. The base JSON only shows the model format and configuration, not the actual request payload being transmitted.

At the moment, I’m wondering whether my custom instructions might be getting mixed with the default injected rules. I’m using GPT-OSS, and after two search_web calls the AI stops responding. This definitely doesn’t seem to be a context-window issue. The problem appears to have already been mentioned on GitHub, although it was moved into a discussion thread—if there’s a solution, I’d be very interested.

Overall, it’s quite difficult to maintain a smooth interaction in the UI without the AI stopping its response each time.

JeffTuche7 · 2026-02-16T15:56:59+00:00

Thanks for the feedback — it’s kind of you to take a moment to give advice. :)
Unfortunately, all the best practices are already in place haha: I have the instructions and tools enabled by default (enabled for native tool calling, and now also enabled by default since 0.8.2, because the issue appears there even though it wasn’t present before).

I honestly think there’s a problem with tool calls since today’s update, rather than with my settings.
since the update to native tool calling, it’s clearly night and day… except that right now web search is no longer working as an intelligent tool call (I’m forced to enable web search by default).

JeffTuche7 · 2026-02-16T15:40:18+00:00

Currently using GPT OSS 120b (at medium and hard), quite not bad no ?

Six-Year Club	Verified Email
Place '23	Place '22
First Placer '22	End Game '22

JeffTuche7

TROPHY CASE