# How to speed up Agent's response time?

**URL:** <https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552>\
**Category:** Product Support\
**Tags:** ai, ai-bot\
**Created:** [16 בנובמבר,‏ 2026,‏ 3:50pm UTC](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552 "2026-11-16T15:50:40Z")\
**Posts on this page:** 4\
**Page:** 1

## סיכום מבוסס בינה מלאכותית

In the [Product Support](/t/-/417552/1) discussion, [putty](/t/-/417552/1) seeks advice on reducing [Agent](/t/-/417552/1) response time for a single conversation powered by [GPT Sol 6.1](/t/-/417552/1) and extensive RAG. [Falco](/t/-/417552/2) provides [several optimization strategies](/t/-/417552/2):

1. **Reasoning Effort**: Try lowering the setting (e.g., `Sol on low`) for better speed.
2. **Service Tier**: Enable the `priority` tier ("Fast mode") for a 2.5x speed increase, with `ultrafast` potentially available.
3. **Prompt Caching**: Structure prompts to maximize cacheability and reduce prefill time.
4. **RAG vs. Hardcoded Prompt**: Depending on the knowledge base size, a large static prompt may be faster than dynamic RAG loading.
5. **Optimize Tools**: Ensure custom tools for dynamic grounding are highly efficient.
6. **Model Choice**: Consider switching to a smaller model like [Luna](/t/-/417552/2) if quality trade-offs are acceptable.

[putty](/t/-/417552/3) also asks about using [subagents](/t/-/417552/3) to split up product components and streamline RAG. [Falco](/t/-/417552/4) [cautions](/t/-/417552/4) that while subagents can help, they are complex and high-maintenance, recommending they be considered only after trying the easier optimizations above.

<div class="post-metadata">

**Author:** ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)\
**Post date:** [16 בנובמבר,‏ 2026,‏ 3:50pm UTC](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552/1 "2026-11-16T15:50:40Z")

</div>

What settings do you recommend tweaking or increasing to reduce response time? **Assume I’m only talking about a single conversation, not dozens running at the same time.** Aside from trimming down the prompt/RAG, it seems like `Thinking Effort` is the only setting that really affects timing for an individual conversation.

For background, I have an agent equipped with GPT Sol 6.1 and loaded with our product documentation, knowledge base articles, and some “gotcha” questions and answers.

I _just_ noticed a subagent setting. I wonder if I can use this to split up some product versions/components and streamline the RAG?

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [16 בנובמבר,‏ 2026,‏ 4:09pm UTC](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552/2 "2026-11-16T16:09:11Z")

</div>

1. Reasoning effort  
Sol on low is very capable; I use it extensively for many tasks, so I’d try that first.

2. Service Tier  
Discourse also supports the service tier `priority`, which is the same as “Fast mode” and makes it 2.5 times faster. We could add `ultrafast` as an option there if you want it faster.

3. Prompt caching  
Move all the dynamic parts of your prompt as late as possible to increase what is cacheable and reduce prefill time.

4. Experiment with the RAG + tools vs hardcoded prompt tradeoff  
Depending on how big your KB is, sometimes using a very large prompt will be quicker and cheaper than dynamic loading of knowledge.

5. Faster tools  
If you, like we do on [ask.discourse.com](http://ask.discourse.com), make extensive use of custom tools for dynamic grounding sources, optimizing those to respond ASAP is very beneficial.

6. Smaller Models  
Depending on your use case, switching to Luna may close the speed gap with acceptable quality.

---

<div class="post-metadata">

**Author:** ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)\
**Post date:** [16 בנובמבר,‏ 2026,‏ 4:11pm UTC](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552/3 "2026-11-16T16:11:37Z")

</div>

Thank you! I’ll definitely try all of these.

> [@putty](#):
>
> I _just_ noticed a subagent setting. I wonder if I can use this to split up some product versions/components and streamline the RAG?

Any thoughts on the effectiveness of subagents in this case? That would really help me trim some fat on the RAG.

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [16 בנובמבר,‏ 2026,‏ 4:19pm UTC](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552/4 "2026-11-16T16:19:31Z")

</div>

It can definitely help, but it is also the hardest one in terms of labor, and maintenance going forward, so I’d reach for it only if it still doesn’t feel right after you explored the low hanging ones.
