# Fluid.ampgate~ CPU usage
**URL:** https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949
**Category:** Bug Reports and Issues
**Created:** [August 12, 2021, 5:53pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949 "2021-08-12T17:53:15Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@DominicThibault](https://discourse.flucoma.org/u/DominicThibault)
#### Post date: [August 12, 2021, 5:53pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/1 "2021-08-12T17:53:15Z")
Hello everyone!
I’ve recently started using the flucoma objects in my Max patches. I want to build a simple recording device that will start recording when the loudness of the incoming sound is above a certain threshold and stop when it’s below another threshold . I was gonna use fluid.ampgate~ but came across extreme CPU load. Loading a single object generates an average of 90% CPU usage with peaks above 100%.
I dont’ know if I’m doing anything wrong in the instantiation of the object or if it relates to my system. Here’s the info that I can gather :
- MacOS 10.14.6
- Max 8.1.10
- Attributes for the fluid.ampgate~ object : @minlengthabove 4410 @minlengthbelow 44100 @highpassfreq 80
Thanks for your help!
Dom
---
### Author:  [@DominicThibault](https://discourse.flucoma.org/u/DominicThibault)
#### Post date: [August 12, 2021, 6:45pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/2 "2021-08-12T18:45:53Z")
After a bit of investigation : the @minlengthabove and @minlengthbelow attributes are extremely heavy on the CPU.
I’m not quite sure how different @rampup and @rampdown are to the attributes mentioned above. They seem to behave similarly but cost barely anything in terms of CPU usage.
Clarification here would be appreciated. 🙂
Dom
---
### Author:  [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [August 12, 2021, 11:12pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/3 "2021-08-12T23:12:09Z")
Hi @DominicThibault,
Thanks for the report. The `minlength` attributes do add CPU load, but spikes of that order sound worrying. The difference between these and the `ramp` attributes is that the latter simply do, effectively, what `slide~` does and apply (very cheap) exponential smoothing to the detection signal. The `minlength` attributes, OTOH, are doing full lookback / ahead. I’ll make an issue on GitHub and run your settings with a profiler to see what’s up.
---
### Author:  [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [August 12, 2021, 11:18pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/4 "2021-08-12T23:18:46Z")
Logged at
>
>
> via https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949
>
> Reports of CP…U hitting 90-100 % with the \`minlength\` attributes set in the order of 100 - 1000 ms. Will profile...
I’ll try and take a look tomorrow
---
### Author:  [@DominicThibault](https://discourse.flucoma.org/u/DominicThibault)
#### Post date: [August 18, 2021, 5:48pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/5 "2021-08-18T17:48:40Z")
Thanks!
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [August 22, 2021, 3:41pm UTC](https://discourse.flucoma.org/t/fluid-ampgate-cpu-usage/949/6 "2021-08-22T15:41:57Z")
Definitely an old known bug but nobody but me flagged it before 😉 There is a fix in the PR if you fancy an adventure in compiling-land.