Ridiculous profiler memory usage of Min/Max Components

Replies to This Discussion

Permalink Reply by Oliver Brossmann on March 14, 2017 at 4:43pm

The percentage that shows underneath the components doesn't correspond to memory, but instead corresponds to % of computation time. Since you only have a few other components on your canvas the percentage is very high for the min/max calculation. It is still only taking 5 milliseconds to compute. As soon as you create more components that calculation % will drop significantly.

Permalink Reply by David Rutten on March 14, 2017 at 5:12pm

Also note that the first time a component runs it will take longer because it has to be compiled. So you typically can't trust those profiler values until after all components have run several times.

I don't recognise the icon though, which component is it? 5ms for a min/max search of 12 values does sound excessively long.

Permalink Reply by Daniel on March 15, 2017 at 12:25am

Thanks, it was Min/Max component

Permalink Reply by David Rutten on March 15, 2017 at 2:24am

Yeah but where did it come from? Which plug-in provided it?

Permalink Reply by Daniel on March 15, 2017 at 2:26am

Sorry, it's Heteroptera I didn't realize it was a plug-in.

Permalink Reply by Daniel on March 15, 2017 at 2:28am

It explains also computation time as well.

Permalink Reply by David Rutten on March 15, 2017 at 4:30am

Maybe. You can do this directly in Grasshopper as well. The Bounds component in the Domain panel creates a numeric interval which encompasses a collection of numbers. If you then extract the lower and upper limits of this bounding domain, it's basically the same as the minimum and maximum value. This approach requires two components, so at least currently your file is simpler.