since 5.1 a few nodes had a new UI introduced which causes some regressions. One of which is that opening and loading the configuration window takes several seconds. I opserved it across sifferent nodes such as (not comprehensive):
You may also notice the unproportionally height of the window. I opened a feature suggestion once but related to the circumstance that a column with a very long column name is present. Now this issue of unproportionally sized windows really becomes an annoyance.
I couldn’t notice an unexpeted lag for the configuraiton dialg of the nodes you have mentioned. Maybe it’s worth it to try this issue as well while testing the other issue you have mentioned here:
I guess the many topics I raised converge around the scenario when there is a string column with very long strings (in total around 1.3 GB distributed across 1697 rows). However, I was not able to reproduce the delay.
Concluding I’d say, since I have opened a few topics around stability, that some symptoms occur occasionally. I shared the data in question with @carstenhaubold. Though, there also seems to be some odd influx in data stored when images are present in a column (~1.5 GB to > 20 GB) which I raised as well.
If that issue appears again or I can isolate / reproduce it, I will let you know. Eventually it gets resolved alongside other topics or never appears again.
I was able to reproduce the issue and it turns out that it is related to having lots of columns. Might also be the case if you have very long column names. We are currently investigating on how to improve the performance for these cases.
We have already found one problem that causes the input lag you have reported in another thread and the solution should soon land in the nightly. I will update this and/or the other thread once that is the case and I would be grateful if you could try it out and report if this solves your problem.
glad to hear that. I tried to check and verify the nighty build but am unable to start Knime. I have create a topic for that (initially bit 4.7) and also referenced it in another post. I have no clue how to resolve that.
