# Make CData Sync go even faster

**URL:** <https://community.cdata.com/t/make-cdata-sync-go-even-faster/514>\
**Category:** CData Sync\
**Tags:** question, cdata-sync, snowflake, redshift\
**Created:** [November 8, 2023, 2:14am UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514 "2023-11-08T02:14:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![worldwidehow](https://avatars.discourse-cdn.com/v4/letter/w/f6c823/32.png) [@worldwidehow](https://community.cdata.com/u/worldwidehow)\
**Post date:** [November 8, 2023, 2:14am UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514/1 "2023-11-08T02:14:58Z")

</div>

is it possible for us to configure&nbsp;CData Sync to use more RAM of the VM? For example, when I do a initial replication&nbsp;of&nbsp;1mil records from Redshift (RA3.16xlarge)&nbsp;to Snowflake (medium wh).. it takes roughly 3 mins.. I noticed Cdata is using only ¼&nbsp;of the total 32GB RAM available.

---

<div class="post-metadata">

**Author:** ![Ankit\_Singh](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/ankit_singh/32/1614_2.png) [@Ankit\_Singh](https://community.cdata.com/u/Ankit_Singh)\
**Post date:** [November 8, 2023, 7:34am UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514/2 "2023-11-08T07:34:07Z")

</div>

Hi @worldwidehow

I believe you are looking for utilizing more RAM and wish to increase the performance of the job. Is that correct assumption? If yes, you can increase the **Batch Size** of the job.

I have mentioned this here:

> **[Batch size / Commit size for Snowflake target | Community](https://community.cdata.com/cdata-sync-47/batch-size-commit-size-for-snowflake-target-536?tid=536&postid=1035#post1035)**
>
> Hey @DougN Nouria  | Hello,Has anyone experimented with different batch sizes while sending data into Snowflake?  It looks like the default is 100000 rows.  I am wondering if there are any downsides to trying a higher number.Thanks!

To increase the Batch Size of the Job, refer to the Advanced Job Options here:&nbsp;[CData Sync - Advanced Job Options | 22.0.8483](https://cdn.cdata.com/help/ASH/sync/Advanced-Job-Options.html).

Let me know if this helps!

---

<div class="post-metadata">

**Author:** ![worldwidehow](https://avatars.discourse-cdn.com/v4/letter/w/f6c823/32.png) [@worldwidehow](https://community.cdata.com/u/worldwidehow)\
**Post date:** [November 8, 2023, 8:06am UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514/3 "2023-11-08T08:06:57Z")

</div>

hi @Ankit_Singh &nbsp; yes, i increased it to 1mil.. and it is taking 3mins. the entire table is 229mil records.. any other ways to make CData Sync go faster or utilise more RAM of the VM?

---

<div class="post-metadata">

**Author:** ![DougN\_Nouria](https://avatars.discourse-cdn.com/v4/letter/d/e0b2c6/32.png) [@DougN\_Nouria](https://community.cdata.com/u/DougN_Nouria)\
**Post date:** [November 13, 2023, 3:57pm UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514/4 "2023-11-13T15:57:19Z")

</div>

Just to confirm…&nbsp;where is Sync deployed, in your scenario?&nbsp; In a VM on AWS, or, on your company on-premises network?&nbsp; The latter would introduce some notable delays in a cloud-to-cloud scenario.

---

<div class="post-metadata">

**Author:** ![worldwidehow](https://avatars.discourse-cdn.com/v4/letter/w/f6c823/32.png) [@worldwidehow](https://community.cdata.com/u/worldwidehow)\
**Post date:** [November 14, 2023, 5:53am UTC](https://community.cdata.com/t/make-cdata-sync-go-even-faster/514/5 "2023-11-14T05:53:48Z")

</div>

> [@DougN\_Nouria](#):
>
> Just to confirm…&nbsp;where is Sync deployed, in your scenario?&nbsp; In a VM on AWS, or, on your company on-premises network?&nbsp; The latter would introduce some notable delays in a cloud-to-cloud scenario.

hi, Sync is deployed in Azure VM. My data source is on AWS Redshift&nbsp;(RA3.16xlarge) and my destination is Azure Snowflake (Medium WH).

Do you have any notes or links to show how CData Sync and its VM has been set up to replicate very large tables (i.e. 50GB, 100GB) for initial data loading purpose and there is no attribute to do incremental loading.
