# Computation time does not scale with SetMetricSamplingPercentage setting in ITK V4

**URL:** https://discourse.itk.org/t/computation-time-does-not-scale-with-setmetricsamplingpercentage-setting-in-itk-v4/1798
**Category:** Algorithms
**Tags:** registration
**Created:** [April 17, 2019, 8:34pm UTC](https://discourse.itk.org/t/computation-time-does-not-scale-with-setmetricsamplingpercentage-setting-in-itk-v4/1798 "2019-04-17T20:34:25Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![dzenanz](https://discourse.itk.org/user_avatar/discourse.itk.org/dzenanz/32/1093_2.png) [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [April 17, 2019, 9:21pm UTC](https://discourse.itk.org/t/computation-time-does-not-scale-with-setmetricsamplingpercentage-setting-in-itk-v4/1798/2 "2019-04-17T21:21:00Z")

</div>

- V4 registration should be neither significantly slower nor take significantly more memory, if the settings are equivalent.
- SetMetricSamplingPercentage should have an effect. See a related [discussion](https://discourse.itk.org/t/sampling-strategy-in-imageregistrationmethodv4/1038).
- The old registration classes are still supported, so you don’t have to switch to V4 registration framework. Unless you have a good reason to switch to V4 framework, I suggest you stick with the old one. V4 framework is more flexible (and complicated), with many differences including different defaults for some things. If you switch to V4 registration framework, you will have to re-tune your parameters, at least to some degree.

---

_[View the full topic](https://discourse.itk.org/t/computation-time-does-not-scale-with-setmetricsamplingpercentage-setting-in-itk-v4/1798)._