# General Config for go client

**URL:** <https://discuss.aerospike.com/t/general-config-for-go-client/4384>\
**Category:** Configuration\
**Tags:** go\
**Created:** [July 13, 2017, 7:04am UTC](https://discuss.aerospike.com/t/general-config-for-go-client/4384 "2017-07-13T07:04:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ajay\_Bodhe](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Ajay\_Bodhe](https://discuss.aerospike.com/u/Ajay_Bodhe)\
**Post date:** [July 13, 2017, 7:04am UTC](https://discuss.aerospike.com/t/general-config-for-go-client/4384/1 "2017-07-13T07:04:38Z")

</div>

I am going to use aerospike in project that I am going to build for personal use. Let me know what configuration I should use for GOLANG client esp this is going to be highly concurrent application with serving 2k-5k reuests per second.

How should I configure client connection, buffer poooling settings so that goroutines dont end up waiting for these resources?

Also I can see from code: type ClientPolicy struct { // ConnectionQueueCache specifies the size of the Connection Queue cache PER NODE. ConnectionQueueSize int //= 256

```
    // If set to true, will not create a new connection
    // to the node if there are already `ConnectionQueueSize` active connections.
    LimitConnectionsToQueueSize bool //= true

```

} Does this mean max 256 goroutines can simultaneously make cache calls?

Also let me know the meaning of and the effect on scaling of the client: service\_threads: 4 transaction\_queuers: 4 transaction\_queues\_per\_thread: 4 proto\_fd\_max 15000