Hi, My use-case is a cloud environment, as an example a continuous integration process that runs dfx deploy in a dfx start --emulator local network. When testing locally, noticed that after the first run and the existence of the .dfx directory, the dfx deploy is a bit faster. In the cloud environ…

Here’re some high-level notes (of course that is not so linear, especially if you consider that it’d run in the cloud). Managed to reduce a 20m build to 5~8m. My use-case is a test runner, in which git clone’s a remote repository and performs tests against it. This is a Rust project for the IC. A…

The only thing I can think of is only re-deploying the canister’s that have actually changed. e.g. if you have 10 canisters listed in dfx.json, dfx deploy will rebuild all 10 even if only 1 has changed. The other route is: dfx build <canister id> dfx canister install <canister id> --mode upgrade T…

That’s correct! Although for the cloud version, running in a CI is trickier as I’d have to write logic to map changes to particular canister ids, to be picky about updates. Meanwhile, the dfx deploy seems to handle what to upgrade for us, by checking the .dfx directory…

I’m not sure if this works with --emulator, but just in case, you might try: A new --no-artificial-delay option enables you to reduce the time it takes for the local Internet Computer to start. This change adds the --no-artificial-delay flag to dfx start and dfx replica commands. By default, the …

Hi @lsgunn , thanks for your suggestion! I’ll check the flag, wasn’t aware of it :wink:

It was just added in 0.7.1, so it isn’t in the regular doc just yet. Hope it helps you out.

Yeh thanks! Already testing, and locally seems faster already. Will wait for the cloud version (which is a slower environment, running on a VM). By the way, noticed that the 0.7.2 was released. Maybe there’re other new flags, I’ll check!

Just thought about something that might be useful. It was my assumption that the dfx deploy only takes into account the .dfx directory. When the related build commands during dfx deploy, the rust directories might also change, on subsequent calls probably preventing compile times. I’ll cache the ru…

@heldrida this is really good feedback. dfx hasn’t been optimized for a CI environment and there’s a lot of room for improvement here. Like Lisa pointed out, if you use --no-artificial-delay this will speed up the local replica’s consensus, but as you might have already tried, it does not work with …

Thanks for checking out and the feedback so far! I’ll share my findings definitely :wink:

[image] heldrida: Starts the dfx network by using the flags --background, --clean, --emulator.The network process is placed in the background otherwise would block the process. Clean, to prevent errors such as *1 Bad request for non existing canister. I am curious, what was the reason you us…

Dfx deploy, how to make it faster after first build?

Developers

heldrida June 17, 2021, 5:10pm 18

The 500 error has been reported before but no answer, you can find it here: The replica returned Http Error - status 500 Internal Server Error

Topic		Replies	Views
Dfx 0.26.0 Release Command Line Tools dfx	37	874	May 16, 2025
Error Deploying on Locally Built IC Command Line Tools dfx	3	165	June 17, 2024
Dfx deploy locally with a new Dfx identity Command Line Tools	28	3006	January 18, 2023
Why is local deployment so slow? Command Line Tools	6	416	November 25, 2023
Error: Failed while trying to deploy canisters Developers	1	546	November 20, 2023

Dfx deploy, how to make it faster after first build?

Related topics