Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize embedded BoringSSL build #447

Merged
merged 1 commit into from
Apr 3, 2019
Merged

Optimize embedded BoringSSL build #447

merged 1 commit into from
Apr 3, 2019

Commits on Apr 2, 2019

  1. Optimize embedded BoringSSL build

    Don't build unnecessary libraries, binaries, tests, etc. Build only two
    static libraries that we need. This results in considerable time saving
    during the builds: BoringSSL contains quite a few tests and tools which
    we do not run and use, yet they get built.
    
    Native
    ------
    
    Before:
    
        $ time make all ENGINE=boringssl
    
        real    4m36.341s
        user    3m44.060s
        sys     0m33.924s
    
    After:
    
        $ time make all ENGINE=boringssl
    
        real    1m56.910s
        user    1m29.960s
        sys     0m19.392s
    
    Nuff said.
    
    Android
    -------
    
    Before:
    
        $ time ./gradlew --no-daemon --no-parallel --max-workers=2 assembleDebug
    
        real    34m46.028s
        user    29m9.580s
        sys     6m39.280s
    
    After:
    
        $ time ./gradlew --no-daemon --no-parallel --max-workers=2 assembleDebug
    
        real    12m46.028s
        user    9m1.880s
        sys     2m52.020s
    
    Admittedly, the difference may be smaller--as we still have to wait for
    Gradle to download the whole Internet during Android build--but that's
    still a significant improvement because there are four architectures
    that we need to build BoringSSL for.
    ilammy committed Apr 2, 2019
    Configuration menu
    Copy the full SHA
    7a882c0 View commit details
    Browse the repository at this point in the history