# Appropriate RAM size for 100M tracks calculation

**URL:** <https://community.mrtrix.org/t/appropriate-ram-size-for-100m-tracks-calculation/1148>\
**Category:** Uncategorized\
**Tags:** connectomics\
**Created:** [September 1, 2017, 10:41am UTC](https://community.mrtrix.org/t/appropriate-ram-size-for-100m-tracks-calculation/1148 "2017-09-01T10:41:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jdtournier](https://community.mrtrix.org/user_avatar/community.mrtrix.org/jdtournier/32/2594_2.png) [@jdtournier](https://community.mrtrix.org/u/jdtournier)\
**Post date:** [September 4, 2017, 12:25pm UTC](https://community.mrtrix.org/t/appropriate-ram-size-for-100m-tracks-calculation/1148/2 "2017-09-04T12:25:08Z")

</div>

Yes, `tcksift` is pretty RAM-intensive. In any case, maybe [this post](https://community.mrtrix.org/t/sift-to-reduce-tractography-biases-in-tractogram-tcksift/602/5?u=jdtournier) answers your question?

---

_[View the full topic](https://community.mrtrix.org/t/appropriate-ram-size-for-100m-tracks-calculation/1148)._