Skip to content

Add a way to measure incremental rebuilds #106

@BenFrantzDale

Description

@BenFrantzDale

To me, the most important thing isn't how long a full build takes, but rather an incremental build. For example, over the course of the day, as I switch branches, rebase, bisect, etc. I'd love to be able to see stats representing that.

My mental model of ClangBuildAnalyzer is that --start puts a file in the build dir, and that --stop then searches the build dir for all .cpp.json files newer than the "start" file, and analyzes them. Likewise --all just looks at all of them.

To get what I want, I think I'd need to run a script every time I build that...

  1. Searches the build dir for .cpp.json files and
  2. copies them to an output folder as $(sha1sum foo.cpp.json).cpp.json.
    So for example, if I rebuilt foo.cpp three times, I would have three separate .cpp.json files, once for each build.
    Then I'd run CalngBuildAnalyzer on that output folder to find out where my time waiting for builds has actually gone over the course of the day.

Should that work? Is there interest in this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions