# Low read performance per distinct hashing process

**URL:** <https://kopia.discourse.group/t/low-read-performance-per-distinct-hashing-process/90>\
**Category:** Support\
**Created:** [September 6, 2020, 4:21pm UTC](https://kopia.discourse.group/t/low-read-performance-per-distinct-hashing-process/90 "2020-09-06T16:21:03Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)\
**Post date:** [September 9, 2020, 5:48am UTC](https://kopia.discourse.group/t/low-read-performance-per-distinct-hashing-process/90/18 "2020-09-09T05:48:33Z")

</div>

FWIW fixed splitters are not ideal if you have files that are partially modified as they don’t perform content-based splitting.

So if you have a large video file (say 10 GB) and add one byte somewhere at the beginning (for example by changing embedded text metadata), fixed splitter will need to reupload 10 GB. content-based splitters (buzhash and rabin karp) will detect the change and typically only need to upload one or two chunks (\<10MB total).

Fixed splitter will be much faster, though.

---

_[View the full topic](https://kopia.discourse.group/t/low-read-performance-per-distinct-hashing-process/90)._