after upgrading (from 3.6.1) to KNIME 3.7 I encountered serious problems with the Java Snippet node.
Connecting a ‘Java Snippet’ node (freshly dragged/dropped from the repository) with a predecessor (e.g. File Reader) takes 3 seconds to change to ‘yellow-mode’ when done for the first time! (deleting the connection and re-doing it works fine
Opening the dialog of a ‘Java Snippet’ node for the first time (after being connected) takes more than 40 seconds! Opening the dialog the second time takes ~ 3 seconds!
This happens per ‘Java Snuppet’ node you are dragging from the repository!
I’m running KNIME on a WIN10 Prof PC having 32GB ram (24 for KNIME) and an i7.
It seems that I’m either the only one having this problem or the only one using the JavaSnippet node in 3.7:slight_smile:
Here some more info:
- I can reproduce it on different (WINDOWS) machines - including a powerfull server (40 cores) having ‘Windows 2012 R2’ (and no virus scan).
- Opening the config dialogue (F6) of the Java Snippet causes the CPU load to jump from ~3% to ~30%(untill the dialogue appears) - on a 8 core i7!
- In contrast, the ‘Java Snippet(simple)’ node does not have these problems - the config-dialogue opens immediately!
I think this has to do with bundles being loaded while the Java Snippet configuration dialog is opening. We’ll look into it.
In the meantime, can you tell us what extensions you have installed in your KNIME Analytics Platform (File -> Install KNIME Extensions -> “What is already installed?”)?
Also, could you check if you’re also running into the issue when using a fresh KNIME installation from https://www.knime.com/downloads/download-knime without any additional extensions installed?
I haven’t used Java snippets since I switched to KNIME 3.7, but I notice the same slowness with the Python nodes. If you pull out a fresh Python Source node and double click on it, it takes considerable longer to open the config window than it did with KNIME 3.6. However, once you try to re-open the config window for an existing node it behaves with normal speed. So it appears to be a “fresh node” phenomenon.
on my WIN PC I have all Extensions installed. But this slow openening (and consumption of a lot of CPU power) also occured on a ‘fresh’ and minimal Linux installation.
unfortunately 3.7.1 does not fix the problem with the performance of the opening of the JAVA Snippet’s Dialogue. As waiting 40-50 seconds per JAVA Snippet node is not an option for me, I switched back to KNIME 3.6.2…
However, do you have a guess when a fix will be provided?
Yup, this has not been fixed in 3.7.1 unfortunately. We are actively working on it though: we have identified the likely source for the issue and are discussing solutions. I can’t give you an ETA, but I will let you know as soon as we have a fix.
Thanks for bringing this up again though. I do agree that this is super important.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.