# Read time benchmarks for write-block-size

**URL:** <https://discuss.aerospike.com/t/read-time-benchmarks-for-write-block-size/8972>\
**Category:** Operations\
**Tags:** benchmark, query\
**Created:** [November 9, 2021, 3:12am UTC](https://discuss.aerospike.com/t/read-time-benchmarks-for-write-block-size/8972 "2021-11-09T03:12:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vixian](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/vixian/32/1758_2.png) [@Vixian](https://discuss.aerospike.com/u/Vixian)\
**Post date:** [November 9, 2021, 3:12am UTC](https://discuss.aerospike.com/t/read-time-benchmarks-for-write-block-size/8972/1 "2021-11-09T03:12:25Z")

</div>

I have a version 4.2 database with a fairly large number number of records that are approaching the currently configured write-block-size of 1Mb. So, now I need to consider whether or not to shard my data or increase my configured write-block-size. I’ve seen that increasing the write-block-size has negative performance impacts, but I can’t find any specific benchmarks so I can’t tell if it’s better to raise it, or shard my data. Is there anywhere I could find concrete data to help me make this decision?

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [November 9, 2021, 11:34pm UTC](https://discuss.aerospike.com/t/read-time-benchmarks-for-write-block-size/8972/2 "2021-11-09T23:34:02Z")

</div>

The answer will always be **‘benchmark it’**. In my experience I think it more so comes down to a question of if you will ever be using _parts_ of the data or always the whole piece.

If the answer on if you will ever only need to read/write part of the data is ‘yes’, such as “yes sometimes I only need part of the data”, or even “yes sometimes I will only write part of the data”, then the answer is usually that you will benefit from splitting up your records at the cost of extra index space.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [November 9, 2022, 11:34pm UTC](https://discuss.aerospike.com/t/read-time-benchmarks-for-write-block-size/8972/3 "2022-11-09T23:34:33Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.