# How to configure number of threads writting to Disk

**URL:** <https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394>\
**Category:** General Discussion\
**Created:** [July 27, 2018, 1:52pm UTC](https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394 "2018-07-27T13:52:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sameer\_Shelar](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/sameer_shelar/32/1224_2.png) [@Sameer\_Shelar](https://discuss.aerospike.com/u/Sameer_Shelar)\
**Post date:** [July 27, 2018, 1:52pm UTC](https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394/1 "2018-07-27T13:52:26Z")

</div>

What is thread name that flushes data from memory(swb) to Disk ?

How to configure number of threads that flushes data from memory(swb) to Disk? If its not configurable then whats rationale for it

---

<div class="post-metadata">

**Author:** ![rbotzer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rbotzer/32/2114_2.png) [@rbotzer](https://discuss.aerospike.com/u/rbotzer)\
**Post date:** [July 27, 2018, 7:23pm UTC](https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394/2 "2018-07-27T19:23:51Z")

</div>

The [`transaction-queues`](https://www.aerospike.com/docs/reference/configuration#transaction-queues) manage requests from the clients, and by default are set to the number of cores in your cluster node. Each transaction queue has its own pool of transaction threads that access the drives. That’s configurable dynamically by changing the [`transaction-threads-per-queue`](https://www.aerospike.com/docs/reference/configuration#transaction-threads-per-queue). You should benchmark to find whether increasing the threads gives you more performance or not.

For more information read [https://discuss.aerospike.com/t/faq-what-are-the-theories-for-tsvc-timeout/5265](https://discuss.aerospike.com/t/faq-what-are-the-theories-for-tsvc-timeout/5265)

---

<div class="post-metadata">

**Author:** ![Sameer\_Shelar](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/sameer_shelar/32/1224_2.png) [@Sameer\_Shelar](https://discuss.aerospike.com/u/Sameer_Shelar)\
**Post date:** [July 28, 2018, 5:14am UTC](https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394/3 "2018-07-28T05:14:05Z")

</div>

Hi Ronen, Thanks for reply My question is “If transaction threads are producers of write-q then which threads are consumers of write-q” ?

I want to increase number of threads that are consumers of write-q

---

<div class="post-metadata">

**Author:** ![rbotzer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rbotzer/32/2114_2.png) [@rbotzer](https://discuss.aerospike.com/u/rbotzer)\
**Post date:** [July 28, 2018, 6:57pm UTC](https://discuss.aerospike.com/t/how-to-configure-number-of-threads-writting-to-disk/5394/4 "2018-07-28T18:57:37Z")

</div>

It’s not configurable, but you can partition drives to increase the number of devices (each partition is a device in Linux). There will be a `write-q` and associated write thread for each device.

> [@Horizontal scaling (v3.16.0.6)](https://discuss.aerospike.com/t/horizontal-scaling-v3-16-0-6/5392/4):
>
> No problem. You can scale your writes by adding drives to the node (vertically), or by adding nodes with the same number of drives (horizontally). There’s also the impact of partitioning. To be super clear, there’s a write queue per-device, and in Linux a device is a partition, not a drive. To mitigate temporary peaks the streaming write buffers go into the write queue, whose size is controlled by [max-write-cache](https://www.aerospike.com/docs/reference/configuration#max-write-cache). Partitioning the drive and assigning those devices gives you more of that cache …

Just be aware that it’s unlikely your problem is write threads, but rather the overall performance of your drive.