# How to cut runtimes for life-cycle profiles or 'AllStats' when you don't need all the stats (simoptions.whichstats)

**URL:** https://discourse.vfitoolkit.com/t/how-to-cut-runtimes-for-life-cycle-profiles-or-allstats-when-you-dont-need-all-the-stats-simoptions-whichstats/253
**Category:** Uncategorized
**Created:** [December 4, 2023, 3:55am UTC](https://discourse.vfitoolkit.com/t/how-to-cut-runtimes-for-life-cycle-profiles-or-allstats-when-you-dont-need-all-the-stats-simoptions-whichstats/253 "2023-12-04T03:55:37Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![robertdkirkby](https://discourse.vfitoolkit.com/user_avatar/discourse.vfitoolkit.com/robertdkirkby/32/287_2.png) [@robertdkirkby](https://discourse.vfitoolkit.com/u/robertdkirkby)
#### Post date: [July 29, 2024, 12:24am UTC](https://discourse.vfitoolkit.com/t/how-to-cut-runtimes-for-life-cycle-profiles-or-allstats-when-you-dont-need-all-the-stats-simoptions-whichstats/253/5 "2024-07-29T00:24:12Z")

</div>

There is now a `simoptions.whichstats(6)=2` which makes calculating the quantiles faster.

Does exactly the same thing as `simoptions.whichstats(6)=1`, but the code is vectorized rather than loop, so faster. It can cause out of memory errors in larger models with large numbers of quantiles, hence is not the default which remains `simoptions.whichstats(6)=1`.

Note: simoptions.whichstats(6) controls the decision to calculate quantiles. So now setting it to zero skips calculating quantiles, setting it to one calculates quantiles, setting it to two calculates quantiles faster but using more memory.

---

_[View the full topic](https://discourse.vfitoolkit.com/t/how-to-cut-runtimes-for-life-cycle-profiles-or-allstats-when-you-dont-need-all-the-stats-simoptions-whichstats/253)._