On Thursday, September 1, 2016 at 8:55:23 AM UTC-7, 33th...@gmail.com wrote:
> Ah, I see. Okay, I read that wrong :)
>
> What's the scheduling type on your node? I believe you still need to tell a
> node to execute in parallel eval by setting its scheduling type.
>
> Are you compiling in debug
Ah, I see. Okay, I read that wrong :)
What's the scheduling type on your node? I believe you still need to tell a
node to execute in parallel eval by setting its scheduling type.
Are you compiling in debug? That will be slower too.
But seriously, those geometry iterations are expensive to cr
Hey!
I know that CPU usage is a poor statistic, however I would have thought
that my node which does nothing except read a value would have less of an
impact than a node that is doing actual computations. CPU usage when using
my node jumps up to a higher usage than it does when a full productio
On Thu, 1 Sep 2016, 6:00 PM wrote:
> Hi, I don't necessarily agree with the idea that an increase in cpu usage
> dictates a performance increase in your node. Low cpu usage doesn't mean
> your node or code is slow. cpu usage is not a very good way to gauge the
> performance. Even frame rates wo
Hi, I don't necessarily agree with the idea that an increase in cpu usage
dictates a performance increase in your node. Low cpu usage doesn't mean your
node or code is slow. cpu usage is not a very good way to gauge the
performance. Even frame rates would be better, but the profiler would be
