About this:
It only exists on the api, as I’ve said several times already, I’m using the cli
The CLI is a wrapper around the API. Yes, the CLI does other things beyond just allowing API access but at its core - it’s just an API wrapper. The API is where the support must be added. Once that API endpoint exists the CLI can be extended to use it.
No changes can happen for the CLI until the API endpoint is created. This is why the feature request is on the API. That is the starting place for adding this support.
About this:
Slow (30+ mins)
Netlify App
Quick (2mins)
Netlify App
If examine the messages at the very top of both deploys, the slower one says this:
- 17028 new files uploaded
17022 generated pages and 6 assets changed.
While the faster one says this:
- 7 new files uploaded
1 generated page and 6 assets changed.
The slower deploy had 17251 files and 17028 of those were new. All 17028 files needed to be uploaded to Netlify. All of those files also needed to be analyzed for post-processing (as post-processing is enabled for this site).
The faster deploy actually had more files than the slower deploy. (The faster one had 17278 which is 27 more than the 17251 in the slower deploy.) However, despite having more files, it was much faster. This is the behavior I’ve been talking about.
This second deploy is faster because the API only needed the one new file and six changed files to be uploaded. As only seven files were new or change, only seven file needed to be checked for post-processing. The other 17271 files did not need to be uploaded because all have already be uploaded during previous deploys. The other 17271 files didn’t need to be post-processed for this deploy because it was also done during previous deploys. The post-processing is only needed for the new or changed files.
To summarize, the slower deploy uploaded and did post-processing for 17028 files. The faster deploy uploaded and did post-processing for only 7 files.
Also, your site might not even need the post-processing. By this I mean it is enabled but it might not be providing much benefit to the site. For example, most modern frameworks do the same code minifying we do automatically. If your framework does so already, there is no point in doing it a second time at Netlify. You could test disabling that feature here and making a new deploy:
https://app.netlify.com/sites/gmzh/settings/deploys#post-processing
That won’t change the file upload times. However, it will completely remove the time spent on post-processing. For the slower deploy, the post-processing was about half of the deploy time. Removing the post-processing would reduce the deploy time significantly for your deploys with many new or changed files.
Please let us know if there are remaining questions.