# Working with a huge data chunks

**URL:** <https://discuss.ocaml.org/t/working-with-a-huge-data-chunks/3955>\
**Category:** Learning\
**Created:** [June 19, 2019, 9:41am UTC](https://discuss.ocaml.org/t/working-with-a-huge-data-chunks/3955 "2019-06-19T09:41:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![avsm](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/avsm/32/6_2.png) [@avsm](https://discuss.ocaml.org/u/avsm)\
**Post date:** [June 19, 2019, 12:55pm UTC](https://discuss.ocaml.org/t/working-with-a-huge-data-chunks/3955/2 "2019-06-19T12:55:04Z")

</div>

The answer really depends on why the use of `mmap` is now slow. Are you accessing the data sequentially, or random access? Do you just want to stream them and write out as soon as possible, or do you need more structured patterns?

Once you figure out what the best underlying mechanism to access the files from the operating system is, you can then come up with a suitable abstraction depending on what that is.

---

_[View the full topic](https://discuss.ocaml.org/t/working-with-a-huge-data-chunks/3955)._