# 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:** 1\
**Showing post:** 2

<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.

---

_[View the full topic](https://meta.discourse.org/t/how-to-speed-up-agents-response-time/417552)._
