# Saving Workflow takes extreemly long in 5.1

**URL:** <https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020>\
**Category:** Feedback & Ideas\
**Tags:** bug\
**Created:** [July 24, 2023, 10:15am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020 "2023-07-24T10:15:24Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [July 24, 2023, 10:15am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/1 "2023-07-24T10:15:24Z")

</div>

Hi,

with the recent update to 5.1 I happen to notice that saving a workflow requires considerably more time. I had already saved and restarted a few times but the overall performance during a save seems to be considerably slower.

The workflow in question took about a minute to start saving and than progressed rather slowly and with inconsistent saving times upon each save compared to the previous Knime version.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/3/d/3d8412bba5a121190adff619e8ce0032fc1cc02b.png)

The workflow does only contains very basic text based data, though. about 30k rows with not that many columns. Something feels not quite right.

Best  
Mike

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 28, 2023, 9:54am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/2 "2023-07-28T09:54:24Z")

</div>

Hi @mwiegand,

Thank you for your feedback.  
Does it happen to all workflows or to a specific workflow?  
Is it possible for you to provide an example workflow/instructions so we can replicate the issue?

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [July 28, 2023, 11:06am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/3 "2023-07-28T11:06:33Z")

</div>

Hi @armingrudd,

so far the experience was erratic but I didn‘t had the chance to test a variety of workflows, though.

The primary difference to other workflows I had is that the table contained images. Just a few hundred, though, which collectively account for a few hundred, maybe 1 GB worth if data.

However, I saved in between steps and all nodes were already cached / written to the disc.

At the moment I am on the move nit having access until beginning of the next week to my workstation. If I can identify more circumstances or reliably reproduce the issue, I will let you know immediately.

Best  
Mike

---

<div class="post-metadata">

**Author:** ![Fernando](https://forum-cdn.knime.com/user_avatar/forum.knime.com/fernando/32/30018_2.png) [@Fernando](https://forum.knime.com/u/Fernando)\
**Post date:** [September 26, 2023, 4:35am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/4 "2023-09-26T04:35:01Z")

</div>

Hi,  
I am experiencing exactly the same problem. Knime has become extremely slow when updating to 5.1. On top of that, when saving workflows it takes for ever.

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 4, 2023, 2:19pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/5 "2023-10-04T14:19:00Z")

</div>

Coming back to this since @Fernando brought it back up. Knime, maybe Windows 11 or both seem to have a serious performance issue when writing data to disk.

I created this workflow to easily create large amount of different data types.

> **[Impossible to filter Large Data Sets – mwiegand](https://hub.knime.com/mwiegand/spaces/Public/Knime%20Forum%20Support/Impossible%20to%20filter%20Large%20Data%20Sets~mrZeIru8LGz8uBMw/current-state)**
>
> Solutions for data science: find workflows, nodes and components, and collaborate in spaces.

When trying to write them to the disk, write speeds briefly burst to several hundreds of MB and then plummet down. Contrary to tests the write speed is far slower then expected indicating some sort of bottle neck:

5 GB Test file

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/5/3/53b53e44ba1a698997ad0c42b65ceebcc7089c27.jpeg)

> **[TEST: Western Digital WD\_BLACK SN850X 2TB](https://ssd-tester.de/western_digital_wd_black_sn850x_2tb.html)**
>
> Ergebnisse des Performance / Geschwindigkeits / Benchmark Test: Western Digital WD\_BLACK SN850X 2TB M.2 SSD (AS SSD Benchmark, HD Tune Pro, SSD-Z, CrystalDiskMark)

Without whitelisting in Windows Defender

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/d/0/d08bc0ea6a3c5556dc19f9b2c0bfdf6c6e86b9ac.png)

After whitelisting Knime

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/4/5/45e90e6d8c5254a54dc16014e490c0b6b131a036.png)

It’s been about ten minutes since the prev. screenshot and the SSD is not thermal throttleing. Yet, Knime is still writing but as seen above, it seems not to the second disc “E” as it is pretty much idle.

10 minutes later

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/d/1/d1292cd482381ea6ef5b23247a2cf4154803a72c.png)

@armingrudd there have been quite a few topics in the recent past about performance a regression. The not officially acknowledged Window fix of slow SSDs is installed but I do not see any improvement. Regardless of the backend type, row or columnar based, writing data should be … fast.

Yet, Knime or Winbdows (I really don’t want to blame any app here) seems to behave odd to say the least while writing data without writing data as the 2nd SSD is idle.

> [@KAP 5.1.1 Slow Load Times](https://forum.knime.com/t/kap-5-1-1-slow-load-times/72735/2):
>
> Hi @rfeigel, Would you let us know which operating system are you using and if on windows, are both versions zip archives? Also, is it the same if you start a fresh instance of 5.1.1? or does it get slow when there are extensions installed? Is your 5.1.1 loading time the same with a new workspace? And have you tested them under the same conditions? I mean in the same invironment with the same resources? I would appreciate it if you provide us with this informatin. Thank you!

> [@Ways to speed this up? 10M + rows](https://forum.knime.com/t/ways-to-speed-this-up-10m-rows/70179/53):
>
> Hi all, I’d like to circle back to this topic as I recently read about a regression caused by Windows which was presumably fixed lately. However, Microsoft wasn’t quite specific so the exact circumstances are illusive. Nevertheless, it might be a possible explanation or contribution to the experienced degression. Maybe someone else has more background information or got some “good news” as Professor Hubert J. Farnsworth would say … Best Mike

I hope the workflow above helps.

Best  
Mike

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [October 4, 2023, 3:28pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/6 "2023-10-04T15:28:43Z")

</div>

Thank you @mwiegand for the detailed information.

May I ask for an additional info? Would you create and send us the “thread dump” in [VisualVM](https://visualvm.github.io/) as explained [here](https://www.knime.com/faq#q29).

Thanks again for your valuable feedbacks.

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 4, 2023, 3:46pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/7 "2023-10-04T15:46:08Z")

</div>

You are most welcome. I ave this some addition thought and at came to the conclusion that the possible issue must get narrowed down before. Therefore I converted all special column types to string in order to save it to my primary disk, same type of WD\_BLACK SN850X 2TB M. 2 SSD, but as CSV.

Worth to note in advance is that I quickly paid the groceries store a visit an the table writer didn’t even reached 1 %.

Surprisingly the CSV writer seems substantially faster but peaking at around 140 MB/s. Circa 15 minutes in it reached 13 %. What intrigues me is the fluctuating throughput which, from my perspective, is massively hampering the performance.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/9/d/9d0a94cfdee7fd93259ffc11fd224b22d82f0637.jpeg)

About VisualVM to create a thread dump I got to familiarize myself with a few things first to overcome a few hurdles like:

![image](https://forum-cdn.knime.com/uploads/default/original/3X/e/2/e2438a122bc18c3291c42fbc3914295b3cfad859.png)

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [October 4, 2023, 4:04pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/8 "2023-10-04T16:04:05Z")

</div>

Dear @mwiegand,

You can download JDK from [here](https://www.oracle.com/java/technologies/downloads/) and the installation is pretty straitforward. It shouldn’t be necessary to do anything else after installing it.

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 4, 2023, 4:05pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/9 "2023-10-04T16:05:14Z")

</div>

Thx for the link. Maybe worth adding it in the FAQ section you shared as well?

Update. Here you go. Knime does not appear as “Eclipse” but a more or less anonymous PID.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/f/5/f5b7bf6cb36bd8acc8804e5431d9ad7eab0bc3c6.png)

[knime-5-1-1-thread-dump.txt](https://forum.knime.com/uploads/short-url/nhFddiuPC9tjtiS1Dfv6yqUZcOE.txt) (79.6 KB)

Is there anything else I can provide? Btw, the CSV writer reached 28 %.

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [October 4, 2023, 4:23pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/10 "2023-10-04T16:23:24Z")

</div>

Thank you again @mwiegand,

We will investigate the issue and get back to you soon.

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 4, 2023, 7:24pm UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/11 "2023-10-04T19:24:35Z")

</div>

Good evening @armingrudd,

A colleague of mine asked in regards to another but still Knime-related question why I am not using a Ramdisk. You might have seen my feature suggestion.

Anyways, I played a bit around and noticed something which might be of help. Despite utilizing a Ramdisk, when I enable gzip compression with the CSV Writer node, performance plummeted even though CPU utilization, which I’d expect to significantly increase, was almost idle.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/a/1/a1edc5bbd2e027dde43b80645882e27217d82729.png)

Within about a few minutes almost 10 GB worth of compressed data got written despite only 23 MB/s throughput.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/a/e/ae38670f96a19b2282e0836b490cad6b42e1c81e.jpeg)

Saving only 10k rows instead of 10 million the CSV is more than 1 GB in size. This begs two questions:

1. Theoretically the 10 million rows (Output of the component) do not fit in the 64 GB of memory. The component simply appends one table to itself utilizing exponential growth. However, this is completed in just a few seconds. Question is, does Knime actually generate the data upon writing the CSV? But how does this compare to saving the workflow which is much faster?

2. The Gzip compression should be much faster and utilize pretty much all cores. Like here when I compress the very same data using WinRAR. Why did compression became the bottle neck and write speed dropped by a factor of more than three from 70 to just 20 MB/s?

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/6/d/6d6bd1ed2d94d2eea9c8fe85e0d70fe36b7c6fd1.png)

Best  
Mike

---

<div class="post-metadata">

**Author:** ![wiswedel](https://forum-cdn.knime.com/user_avatar/forum.knime.com/wiswedel/32/28273_2.png) [@wiswedel](https://forum.knime.com/u/wiswedel)\
**Post date:** [October 5, 2023, 9:15am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/12 "2023-10-05T09:15:25Z")

</div>

From the `knime-5-1-1-thread-dump.txt` file you linked above I can draw these conclusions:

There is one single CPU fully busy deserializing nested data structures

- old date&time types (seeing that also in the workflow screenshot) - certainly worth a test switching to the ‘new’ nodes (not exactly new … they were released in 3.4, so 6 years ago 🙂 )
- these elements are nested in some list cell - so it doesn’t appear to be a plain native cell?
- the table format is the old backend

> **Hiding the relevant part of the log here as it's probably only helpful for developers.**
>
> ```auto
> "KNIME-Worker-25-CSV Writer 3:73" #1346 daemon prio=3 os_prio=-1 cpu=2292984.38ms elapsed=2379.22s tid=0x00000000712f6a60 nid=0x30574 runnable [0x000000007466c000]
> java.lang.Thread.State: RUNNABLE
> at java.util.GregorianCalendar.computeFields(java.base@17.0.5/Unknown Source)
> at java.util.Calendar.setTimeInMillis(java.base@17.0.5/Unknown Source)
> at org.knime.core.data.date.DateAndTimeCell.<init>(DateAndTimeCell.java:256)
> at org.knime.core.data.date.DateAndTimeCellSerializer.deserialize(DateAndTimeCellSerializer.java:77)
> at org.knime.core.data.date.DateAndTimeCellSerializer.deserialize(DateAndTimeCellSerializer.java:1)
> at org.knime.core.data.container.DCObjectInputVersion2.readDataCellPerKNIMESerializer(DCObjectInputVersion2.java:104)
> at org.knime.core.data.container.BufferFromFileIteratorVersion20$DataCellStreamReader.readDataCell(BufferFromFileIteratorVersion20.java:366)
> at org.knime.core.data.container.DCObjectInputVersion2$DCLongUTFDataInputStream.readDataCell(DCObjectInputVersion2.java:245)
> at org.knime.core.data.collection.BlobSupportDataCellList.deserialize(BlobSupportDataCellList.java:256)
> at org.knime.core.data.collection.ListCell$ListCellSerializer.deserialize(ListCell.java:176)
> at org.knime.core.data.collection.ListCell$ListCellSerializer.deserialize(ListCell.java:1)
> at org.knime.core.data.container.DCObjectInputVersion2.readDataCellPerKNIMESerializer(DCObjectInputVersion2.java:104)
> at org.knime.core.data.container.BufferFromFileIteratorVersion20$DataCellStreamReader.readDataCell(BufferFromFileIteratorVersion20.java:366)
> at org.knime.core.data.container.BufferFromFileIteratorVersion20.next(BufferFromFileIteratorVersion20.java:172)
> - locked <0x00000000cc300060> (a org.knime.core.data.container.BufferFromFileIteratorVersion20)
> at org.knime.core.data.container.BufferFromFileIteratorVersion20.next(BufferFromFileIteratorVersion20.java:1)
> at org.knime.core.data.container.filter.FilterDelegateRowIterator.internalNext(FilterDelegateRowIterator.java:130)
> at org.knime.core.data.container.filter.FilterDelegateRowIterator.next(FilterDelegateRowIterator.java:123)
> at org.knime.core.data.container.storage.AbstractTableStoreReader$1.next(AbstractTableStoreReader.java:220)
> at org.knime.core.data.container.JoinTableIterator.next(JoinTableIterator.java:98)
> at org.knime.core.data.container.JoinTableIterator.next(JoinTableIterator.java:98)
> at org.knime.core.data.container.JoinTableIterator.next(JoinTableIterator.java:98)
> at org.knime.core.data.container.JoinTableIterator.next(JoinTableIterator.java:98)
> at org.knime.core.data.container.JoinTableIterator.next(JoinTableIterator.java:98)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.data.append.AppendedRowsIterator.initNextRow(AppendedRowsIterator.java:208)
> at org.knime.core.data.append.AppendedRowsIterator.next(AppendedRowsIterator.java:180)
> at org.knime.core.node.streamable.DataTableRowInput.poll(DataTableRowInput.java:91)
> at org.knime.base.node.io.filehandling.csv.writer.CSVWriter2.writeRows(CSVWriter2.java:181)
> at org.knime.base.node.io.filehandling.csv.writer.CSVWriter2NodeModel.writeToFile(CSVWriter2NodeModel.java:184)
> at org.knime.base.node.io.filehandling.csv.writer.CSVWriter2NodeModel.execute(CSVWriter2NodeModel.java:147)
> 
> ```

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 5, 2023, 9:32am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/13 "2023-10-05T09:32:49Z")

</div>

@wiswedel that is odd as none of the cores were even close to being fully utilized per windows task manager. The table Format was generated by the Test Data Generator Node configured using v1 instead of legacy.

> **[Test Data Generator](https://hub.knime.com/knime/extensions/org.knime.features.testing.application/latest/org.knime.testing.node.datagenerator.TestDataNodeFactory)**
>
> Creates a data table with all common data types. It creates for each data type extreme values for testing of writer/reader or visualization nodes.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/9/a/9abc86799756f78b78fab851754aef0529c58a41.png)

I do recall that I mentioned before that this node, because it generates outdated data types, seems in need of an update. Maybe adding v2 or “most recent” would be an option.

> [@\[Bug\] Date and Time to String fails](https://forum.knime.com/t/bug-date-and-time-to-string-fails/47013):
>
> Hi, while working on an approach to efficiently and quickly, regardless of the size of a data set, inject column types, I converted sample data to strings. While doing so I happen to notice the [Date&Time to String – KNIME Hub](https://hub.knime.com/knime/extensions/org.knime.features.base/latest/org.knime.time.node.convert.datetimetostring.DateTimeToStringNodeFactory) Node seems to struggle to convert the Column Type “Date and Time” to a string as the column is not recognized as a valid input type. In addition…

Nevertheless, I also converted all special data types, including the outdated date&time as well as duration data to simple strings in order to use a CSV writer. Whilst being slightly faster, write speed drops over the course of hours to the same level and basically never finishes.

As far as I understand the nested data must get deserialized which would explain the fluctuating write speeds as seen in this screenshot of mine from before:

 ![](https://forum-cdn.knime.com/uploads/default/original/3X/2/d/2dfc01216ef4fd0a90b965cba0a5fde49a8351e1.jpeg)  
About the backend type, it is the default. I will run some benchmarks to narrow things down like:

1. Removing legacy data
2. Testing with current default row vs. future columnar backend type

Best  
Mike

---

<div class="post-metadata">

**Author:** ![wiswedel](https://forum-cdn.knime.com/user_avatar/forum.knime.com/wiswedel/32/28273_2.png) [@wiswedel](https://forum.knime.com/u/wiswedel)\
**Post date:** [October 5, 2023, 10:36am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/14 "2023-10-05T10:36:27Z")

</div>

That explains it! The “Test Data Generator” node is part of the testing extensions that we use _internally_ (but also community node developers) to write unit tests and workflow tests to guarantee correctness of all sorts of compatibility challenges. It produces data, including deprecated data types, which is not relevant in any real world scenario. KNIME’s type system is very rich and we can tell from history that once in a while there is some community extension that does crazy things, like 3rd party types embedded in collections of variable type etc. This node allows us to simulate some of this.

Again, it’s part of a testing extension, the category is called “KNIME Node Development Tools”.

If you needed some larger data to simulate and stimulate CPU and I/O usage I would use some public benchmark (some kaggle data, for instance this [one](https://www.kaggle.com/datasets/elemento/nyc-yellow-taxi-trip-data)).

---

<div class="post-metadata">

**Author:** ![wiswedel](https://forum-cdn.knime.com/user_avatar/forum.knime.com/wiswedel/32/28273_2.png) [@wiswedel](https://forum.knime.com/u/wiswedel)\
**Post date:** [October 5, 2023, 10:37am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/15 "2023-10-05T10:37:43Z")

</div>

Maybe we should do a reset here and focus on the problem you mentioned in your first post (I realize now that you do have real data at hand). Do you mind extracting a similar file to `knime-5-1-1-thread-dump.txt` using your own custom data?

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 5, 2023, 10:56am UTC](https://forum.knime.com/t/saving-workflow-takes-extreemly-long-in-5-1/71020/16 "2023-10-05T10:56:40Z")

</div>

Thanks for your feedback @wiswedel. When I find some time I will use the kaggle data and upload a topic agnostic workflow or update the one I linked before.

About legacy data types. I’d not wave the presence of these away that easily as I do know that some had, and might still have, Knime version 3 in production. Adding to this, those I referenced are not the ordinary tiny nor even mid-sized businesses. So as far as I can conclude, even thought I helped the aforementioned to update to a more recent version, it is a fairly realistic scenario.
