KNIME 4.6 excessive CPU usage (Mac)

I’ve noticed that KNIME 4.6 (the latest and greatest) seems to progressively increase CPU time on my Macbook Pro (Intel). I’ve adjusted the heap size but no change.

It does this without any activity at all, just leaving the Mac sleeping for a couple of hours just now increased it from around 20% to 120%!

Is this something someone has noticed before?

Cheers,
Sam

Hi @ssq,

thank you for letting us now about the issue you are facing!

I tried to reproduce the issue on my MacBook Pro (intel). So far without success.

I didn’t close my KNIME Analytics Platform last tonight when sending my Mac to sleep, but I didn’t get the described increase today in the morning. Do you have an other tip, how I can reproduce the issue?

Thank you
Kathrin

1 Like

Hi, and thanks for your quick response!

Yesterday I didn’t see it either, and today I have been trying to replicate it. KNIME 4.6 seems to have some strange activity because CPU is varying wildly, 10-30% without myself doing anything. When I terminated all other obvious processes (mail, Teams, Safari), its CPU dropped to almost zero… but when I started working with it, it went up again.

I wouldn’t even have noticed the problem but for the very sluggish response time. I was very quickly editing and testing a workflow with components and it became so bad that I rebooted. It was OK for a while after that, but started consuming CPU soon again. Right now it’s 23% when I’m responding to you.

I only have 8Gb RAM. Any suggestions to tweak values in knime.ini ?

Cheers,
Sam

1 Like

Further to the above. I went away, leaving KNME open, closed the lid and the Macbook went to sleep. I returned, and immediately checked the Activity Monitor, and KNIME was at 108%, rising to 120%, to 128%; then slowly subsiding to now around 21%.

I didn’t use it at all.

Is there some background process that consumes CPU?

Cheers,
Sam

1 Like

Hey Sam,

I am able to reproduce the problem. We are already investigating what exactly is going on and will post an update here once we found a solution.

Greetings,
Daniel

1 Like