# Ways to speed this up? 10M + rows

**URL:** <https://forum.knime.com/t/ways-to-speed-this-up-10m-rows/70179>\
**Category:** KNIME Analytics Platform\
**Created:** [June 30, 2023, 1:31pm UTC](https://forum.knime.com/t/ways-to-speed-this-up-10m-rows/70179 "2023-06-30T13:31:17Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![mlauber71](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mlauber71/32/73590_2.png) [@mlauber71](https://forum.knime.com/u/mlauber71)\
**Post date:** [July 5, 2023, 9:54am UTC](https://forum.knime.com/t/ways-to-speed-this-up-10m-rows/70179/12 "2023-07-05T09:54:58Z")

</div>

@Gavin_Attard you could try and put a Cache node in front of the writer node.

> [@Gavin\_Attard](#):
>
> Faster if i use parquet, but can’t seem to read the data back into the nodes.

What does this mean? What kind of data is in there that you cannot re-load it?

Have you tried to write the parquet data maybe in chunks?

> [@knime assign failed, request status: data overflow incoming data too big](https://forum.knime.com/t/knime-assign-failed-request-status-data-overflow-incoming-data-too-big/65232/2):
>
> @RVC2023 one way to get data from and to R is to use Parquet files. You can use them in one go or you can use chunks which is especially useful if you have large data. The large file can be split into smaller parts. If they have the same structure you could also write them in a loop and later import them back as one file: [image]

Have you tried suggestions from the article like using streaming? Maybe put a cache node in fron of a streaming part.

---

_[View the full topic](https://forum.knime.com/t/ways-to-speed-this-up-10m-rows/70179)._
