# Unable to Process Concurrent User Request

**URL:** <https://discuss.huggingface.co/t/unable-to-process-concurrent-user-request/2385>\
**Category:** Models\
**Created:** [December 1, 2020, 6:43am UTC](https://discuss.huggingface.co/t/unable-to-process-concurrent-user-request/2385 "2020-12-01T06:43:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankitsingi007](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@ankitsingi007](https://discuss.huggingface.co/u/ankitsingi007)\
**Post date:** [December 1, 2020, 6:43am UTC](https://discuss.huggingface.co/t/unable-to-process-concurrent-user-request/2385/1 "2020-12-01T06:43:20Z")

</div>

I am using the [https://huggingface.co/ktrapeznikov/biobert\_v1.1\_pubmed\_squad\_v2/tree/main#](https://huggingface.co/ktrapeznikov/biobert_v1.1_pubmed_squad_v2/tree/main#)  
for the question answering model. I am sending around 50 abstracts from Pubmed and then asking the question. It is working fine for 1 user , but when scale to 10 concurrent users the model is taking too long. Can anybody help

---

<div class="post-metadata">

**Author:** ![FL33TW00D](https://avatars.discourse-cdn.com/v4/letter/f/e0b2c6/32.png) [@FL33TW00D](https://discuss.huggingface.co/u/FL33TW00D)\
**Post date:** [December 1, 2020, 9:19am UTC](https://discuss.huggingface.co/t/unable-to-process-concurrent-user-request/2385/2 "2020-12-01T09:19:50Z")

</div>

There’s a number of avenues that you could use to reduce inference time:

1. Scale your deployment vertically or horizontally.
2. Move to a smaller model.
3. Improve your preprocessing/postprocessing efficiency.