# Curious cliff in upload performance: 64KiB boundary

**URL:** <https://forum.storj.io/t/curious-cliff-in-upload-performance-64kib-boundary/31577>\
**Category:** Developer Discussions\
**Tags:** uplink\
**Created:** [March 29, 2026, 2:09am UTC](https://forum.storj.io/t/curious-cliff-in-upload-performance-64kib-boundary/31577 "2026-03-29T02:09:30Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [April 1, 2026, 1:35am UTC](https://forum.storj.io/t/curious-cliff-in-upload-performance-64kib-boundary/31577/11 "2026-04-01T01:35:47Z")

</div>

> [@arrogantrabbit](#):
>
> Those who don’t – why shall be care abotu their performance?

It’s not about performance of the node, but of uplink. Per [V137.5 - high load? - #54 by littleskunk](https://forum.storj.io/t/v137-5-high-load/30874/54), it is opening 70 streams and waiting for 54 to finish. So the faster we bail out on the 16 slow ones, the less overhead in terms of wasted upload bandwidth there is for uploading on the uplink side.

---

_[View the full topic](https://forum.storj.io/t/curious-cliff-in-upload-performance-64kib-boundary/31577)._