# Cluster tuning cookbook

**URL:** <https://forums.foundationdb.org/t/cluster-tuning-cookbook/520>\
**Category:** Using FoundationDB\
**Created:** [June 19, 2018, 2:35pm UTC](https://forums.foundationdb.org/t/cluster-tuning-cookbook/520 "2018-06-19T14:35:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ajbeamon](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ajbeamon/32/13_2.png) [@ajbeamon](https://forums.foundationdb.org/u/ajbeamon)\
**Post date:** [June 21, 2018, 11:30pm UTC](https://forums.foundationdb.org/t/cluster-tuning-cookbook/520/5 "2018-06-21T23:30:24Z")

</div>

> [@shamatar](#):
>
> For details: system itself is written in GO and uses 16 hyperthreading cores (GOMAXPROC=16). It has one global fdb.Database object (that may be a problem, didn’t find a clear answer if such object is single-threaded inside).

Are you saying that your test is a Go program, or is it the multitest run from above?

In either case, each client process has a single network thread, and it’s possible to saturate that thread. I don’t know if that’s happening to you here, but in order to fully take advantage of a cluster it’s usually necessary to run more than one client process to drive load. To do that, you’ll actually need to start multiple client processes, as we don’t support running multiple network threads in a process.

See also the discussion here: [Benchmarking FoundationDB on AWS - #4 by ajbeamon](https://forums.foundationdb.org/t/benchmarking-foundationdb-on-aws/410/4)

---

_[View the full topic](https://forums.foundationdb.org/t/cluster-tuning-cookbook/520)._