Skip to main content
Question

Huge deployment time using cdf toolkit

  • August 21, 2025
  • 4 replies
  • 57 views

Marwen TALEB
MVP

Hello,

 

We are using cdf toolkit to deploy our data models. We have a relatively a big data models that uses 478 views. Each time we deploy a breaking change our data model architecture (well centric) obliges us to redeploy a new version for all views

We notice a huge deployment time at the dependencies resolution step

2025-08-19T09:34:54+00:00 WARNING [LOW]: Failed to create 478 views: One or more
views do not exist: 'sp_dm_mud_brines_for_ops_real_wview:Activity/0.10'..
Attempting to recover...

The overall deployment time takes 35 mins, this way bigger than our standard CI/CD job duration where we try to keep it under 10min at worst.

 

Is there a way to optimize this please? 

 

Thank you!  

 

 

4 replies

Anders  Albert
Seasoned Practitioner
Forum|alt.badge.img
  • Seasoned Practitioner
  • August 21, 2025

I will log this a feature request, and I think there is a quick fix we can do as well. I will notify you once something is out.


Anders  Albert
Seasoned Practitioner
Forum|alt.badge.img
  • Seasoned Practitioner
  • September 25, 2025

@Marwen TALEB This took a bit longer, but the API issue that is causing `Failed to create 478 views: One or more views do not exist: 'sp_dm_mud_brines_for_ops_real_wview:Activity/0.10`is now fixed in the API. 

Thus Toolkit's recovery mechanism should no longer be necessary, and you should automatically speed up that deployment step now.

In addition, we are planning for a speed up of build and deploy in v0.8 of Toolkit (we are currently in v0.6). This will take some time as we are redesigning some internals to get a speed up.


Marwen TALEB
MVP
  • Author
  • MVP
  • October 2, 2025

Hi ​@Anders Albert , what version exactly include this change please? We are currently using 0.6.20. Thanks


Anders  Albert
Seasoned Practitioner
Forum|alt.badge.img
  • Seasoned Practitioner
  • October 22, 2025

All of them 😀It is an API fix, so you already have it. 

 

FYI: We are working on some speed-up on the whole process. This is targeted for v0.8 which I expect will be Q1 next year.