How Can I Accurately Measure the Size of My Go Project, Including Dependencies?

How to Accurately Determine the Size of a Go Project

While the primary question of this discussion revolves around checking the size of a Go project, the solution provided unveils a deeper understanding of how package dependencies can affect the resulting binary size.

Checking Binary Size

To ascertain the size of a Go project's binary, navigate to the $GOPATH/pkg directory and check the KB sizes of .a files (library binaries). For the gorilla http packages, the sizes on a 64-bit MacOS system are as follows:

284 mux.a
128 securecookie.a
128 sessions.a

Beyond Library Size

However, package size is not the sole determinant of its impact on the executable size. Dependencies also contribute, albeit variably due to shared dependencies among imported packages.

Example: The Impact of Dependencies

Consider the following three programs:

• empty.go: No dependencies (size: 1028 KB)
• http.go: Imports "net/http" (size: 5812 KB)
• mux.go: Imports "github.com/gorilla/mux" (size: 5832 KB)

Despite their functional equivalence, the sizes differ significantly. "net/http" alone adds a notable amount of weight, and "mux" carries an additional overhead due to its dependency on "net/http."

Conclusion

To accurately determine the true impact of package imports on binary size, it is essential to consider not just the size of the library itself, but also its sub-dependencies. This will provide a more comprehensive understanding of how packages contribute to the overall executable size in Go.

The above is the detailed content of How Can I Accurately Measure the Size of My Go Project, Including Dependencies?. For more information, please follow other related articles on the PHP Chinese website!