Skip to content

Commit

Permalink
mage: run mage update steps in parallel (#6871)
Browse files Browse the repository at this point in the history
From the looks of it, none of the update steps interact with each other, so
I don't see a reason to run them serially.

As an example, making a single line change in the otel components file results
in the following timings:

	parallel mage update  9.19s user 1.92s system 366% cpu 3.027 total
	serial mage update  20.20s user 2.93s system 181% cpu 12.748 total
  • Loading branch information
mauri870 authored Feb 17, 2025
1 parent 633272c commit 293092c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion magefile.go
Original file line number Diff line number Diff line change
Expand Up @@ -651,7 +651,7 @@ func commitID() string {

// Update is an alias for executing control protocol, configs, and specs.
func Update() {
mg.SerialDeps(Config, BuildPGP, BuildFleetCfg, Otel.Readme)
mg.Deps(Config, BuildPGP, BuildFleetCfg, Otel.Readme)
}

func EnsureCrossBuildOutputDir() error {
Expand Down

0 comments on commit 293092c

Please sign in to comment.