Thank you! I have installed the new jar, will report back on further issues in case we run into any.
First of all - thanks very much to both of you for so tenaciously pursuing this problem! I am suffering from the same issue and have a critical deadline coming up, but unlike @gmakara I don’t have the luxury of reverting back to KNIME 3.6.
I’ve got a huge workflow originally from KNIME 2.12 that I am now migrating up from KNIME 3.5.2 to KNIME 3.7.1. It contains 7 large MetaNodes with the last containing about 500 individual nodes. Yesterday I couldn’t even open that last MetaNode without my workflow freezing. But after applying your latest patch things are working much better!
Not being able to open the MetaNode has put me on a path of moving all of those nodes out into a separate workflow. I’ve seen discussions on calling one workflow from another, so I’ll look into doing that for these nodes.
But right now I can report that, with the patch, I can:
- open the MetaNode
- select and copy all 500 individual nodes
- paste all 500 into a new workflow
The whole process took almost 30 minutes of waiting but it worked!
1 Like
Could you let us know, if possible, how that paste performance compares to doing it in 3.5.2 (if you’re able to without much difficulty?) ((after your critical deadline has come to pass, of course.))
The same copy-paste in KNIME 3.5.2 took 5 minutes flat!
I happened to have the old workflow up to help me with the porting so it was easy to do.
That’s a surprising performance degradation :- (
Thanks for the report - we’ll look into it.
If you have time after your deadline, and if you feel comfortable doing it, I would like you to get a snapshot dump of the running state of your KNIME (using a program called jstack ( https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr016.html .))
Let me know if you have the time after your deadline passes.
I just opened a new topic that is possibly related to this topic. See: KNIME 3.7.1 Configuration Dialog Displaying Wrong Settings
@quaeler You can have my whole workflow if you want it. It’s confidential so I can’t post it online, but I already have an NDA with KNIME so I can send it directly to you (I’m assuming you are a KNIME employee?). You’ll have to install two plugin collections of nodes to get it to work (a public plugin and a private plugin) but I’m happy to get this to you if you think it will help.
Hi @gmakara - Have you experienced further freezes since installing the 2nd iteration of the patch jar?
I do not think so. Looks much more stable.
Good - thanks for the testing and feedback.
Not to beat a perhaps-dead-horse, but could you give me a bit more detail on this slow copy & paste?
Running 3.7.1 with the 2nd iteration patch described in this thread, i grabbed the 50_Applications/36_Guided_Analytics_for_ML_Automation/01_Guided_Analytics_for_ML_Automation/01_Guided_Analytics_for_ML_Automation workflow from the KNIME public repository which has 1860 nodes; i copied and pasted all the nodes in one go from the original workflow to a new workflow and it completed in 3-ish seconds.
In addition to more details of what you’re doing, could you also try the public workflow so that we have a data common touchpoint?
The forum isn’t thrilled about me uploading a 4.7M GIF, but i put a screen cast of the try here: http://theori.st/take_away/knime/1860_node_copy_paste_patched_371.gif
I may have exaggerated the delay. It did take a really long time, but I remembered later that it took several attempts and I subconsciously added everything up. But I can add a few observations:
-
As I was copying everything from inside a MetaNode (including the MetaNode’s input-output blocks) to a top-level workflow (with no MetaNodes) a lot of branches connecting to the input-output blocks had to be pruned. This seemed to take the UI a lot of extra thinking.
-
As I’ve got so many nodes I spend a lot of time manually re-directing the connection paths to make them all look neat. I originally used the straight-connections but copy-and-pasted into a curved-connections workflow. The UI really seemed to struggle with changing all of the connection directions, and the UI spent a lot of wasted time jumping around the workflow showing you bundles of connections being re-established. I tried again with a straight-connections workflow and it seemed to work better, but there was still a lot of unnecessary jumping around.
I’ve not tried to do anything similar since, but I’ve not noticed a dramatic overall performance degradation in the rest of KNIME 3.7.1.
Just to be clear, I selected 500 individual nodes for the copy-and-paste (not 10 metanodes as you did in your GIF). Sorry - I should have watched your GIF first before replying.
:- ) you’re going to make me make a workflow with 500 nodes on a single level, aren’t you?
While their could be something about nodes being all on the same level, at the end of the day, i did cut and paste 1860 nodes; they weren’t all on the same container level, but they got copied.
The connection conjecture is interesting; i’ll do some local de-construction.
Yes - I agree - I’m seeing that also.
Oh ya - ok… so in that same 1860 node workflow, i went 1 level into the “Training and Validation of Models” metanode, and then started expanding all metanodes in here (and all their metanodes, and all their metanodes, …) I got tired of trying to click on the exact metanode as it became soupier and soupier, but there was a sizeable-but-less-than-500 amount (screenshot below) which i then cut and paste.
Indeed, it both took perhaps 20 seconds for the paste, and also there was a lot of samba-ing of the viewport as something was trying to be calculated.
I’ll file a bug, but imaginably one response might be “this is why we have metanodes - to better visually and performance-wise organize the workflows.”
Thanks for the feedback and insights, btw.
4 Likes
That screenshot is like… terrifying… modern art. It deserves some sort of award 
1 Like
Hi @quaeler - another small but annoying issue with the updated UI has to do with the creating of new Workflow Annotations.
If I’m at the bottom-right-corner of my large workflow and I right-click “New Workflow Annotation” then the new annotation will be created way-up at the top-left-corner of my workflow. I then have to drag it back down to the right-corner.
Which reminds me of another small but even more annoying UI issue. This issue has been a part of the Windows KNIME UI forever. That is, it is very difficult to drag nodes outside of the visible area.
If I want to move one or more nodes in any direction outside of the area I’m viewing (typically further right or further down) then I have to click-and-hold to select the nodes, then move my mouse into a space adjacent to the scrollbar about 1 pixel wide. If I can’t place my mouse on exactly that line then the workflow won’t scroll. A fix would be great!!
Thanks for your patience indulging my rants!
Hi - from back to front - oh yes, it is a long standing complaint that dragging nodes out of the viewport is not user friendly; for 3.7.0 we did some internal testing of alternates but nothing passed mustard. It continues to be an open and debated issue in KNIME.
For the workflow annotation, i attempted to repeat this in 3.7.1 with the above rat’s nest of workflow ( 10.7MB screen capture here: http://theori.st/take_away/knime/new_annotation_371.gif ) and was unable to (it worked as i expected it to - with the annotation being placed basic at the mouse down location of the right click.)
Could you give me some more clues to replicate that? (We should probably open that in a new thread too - so could you respond in a new forum thread?)