# Thank you ReduceMesh and McNeel

**URL:** <https://discourse.mcneel.com/t/thank-you-reducemesh-and-mcneel/129504>\
**Category:** Rhino for Windows\
**Created:** [August 31, 2021, 12:11pm UTC](https://discourse.mcneel.com/t/thank-you-reducemesh-and-mcneel/129504 "2021-08-31T12:11:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Normand](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/normand/32/476050_2.png) [@Normand](https://discourse.mcneel.com/u/Normand)\
**Post date:** [August 31, 2021, 12:11pm UTC](https://discourse.mcneel.com/t/thank-you-reducemesh-and-mcneel/129504/1 "2021-08-31T12:11:53Z")

</div>

To whomever (maybe @Jussi_Aaltonen?): Thanks for ReduceMesh and it being multithreaded. Just reduced a 75mill poyfaces scan to a more managable 10mill without any problems. One question: The “preparing to reduce mesh” took an insane amount of time (40 minutes or so), while the actual reduction took only 15-20 minutes or so. Is this to be expected? I’m running a dual Xeon 2.6 with 96GB of RAM and a RTX4000 GPU - and neither CPU, GPU nor RAM saw more than sporadic activity during the prep phase.  
TIA, Jakob