# Best strategy to handle client overload

**URL:** <https://forums.foundationdb.org/t/best-strategy-to-handle-client-overload/2281>\
**Category:** Using FoundationDB\
**Tags:** performance, bindings\
**Created:** [August 7, 2020, 11:19am UTC](https://forums.foundationdb.org/t/best-strategy-to-handle-client-overload/2281 "2020-08-07T11:19:41Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ex3ndr](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ex3ndr/32/389_2.png) [@ex3ndr](https://forums.foundationdb.org/u/ex3ndr)\
**Post date:** [August 11, 2020, 5:36pm UTC](https://forums.foundationdb.org/t/best-strategy-to-handle-client-overload/2281/10 "2020-08-11T17:36:09Z")

</div>

Well, i _think_ problem is on client side. Entire cluster is a client cluster: if you have same request on every node then it will saturate client and application code. It is not a problem for most other DBs since there are no 5 second limit, but with FDB all transactions start to timeout since client is overloaded.

I suspect that this is mostly client, not our application code. I actually found that our application code could be very performant with FDB and it is usually client saturated before our application (like [Bindings seems to be very slow for a simple operation](https://forums.foundationdb.org/t/bindings-seems-to-be-very-slow-for-a-simple-operation/2275/10)).

---

_[View the full topic](https://forums.foundationdb.org/t/best-strategy-to-handle-client-overload/2281)._