CloudBees Accelerator 7 - pushing the boundaries of build acceleration, again

Written by: Electric Bee

2 min read

Stay connected

Today, CloudBees is announcing the immediate availability of CloudBees Accelerator 7.0 . This release brings significant new innovations and performance enhancements to the market for anyone looking to optimize and accelerate their software build environment.
We have publicly launched and talked about some of the new capabilities of this release already, back in February at the Android Builders Summit – here is a blog about what was presented.
The marquee features of CloudBees Accelerator 7.0 are Parse Avoidance and Dependency Optimization:

  • Parse Avoidance significantly reduces makefile parse time. By caching and reusing parse results, this feature can speed up both full builds and incremental builds.

  • Dependency Optimization improves performance of a build by optimally schedule the workload in the build based on the actual dependencies, efficiently removing any superfluous dependency-information.

Apart from performing the upgrade, existing CloudBees Accelerator customers will be able to take advantage of this release with no necessary changes of their build environment.
Below is a table of some of the internal benchmarks we have run as part of qualifying this release. Both builds are Android-based, with stock vanilla Android Jelly Bean 4.1.1 on the left and CyanogenMod 10.0 on the right.

We were using a 48-core machine for all the benchmarks presented above, percentages in blue refers to the relative performance improvement when Dependency Optimization and Parse Avoidance are enabled.
The columns named “48 agents, Remote” shows the benchmarks when CloudBees Accelerator was configured in a distributed build cloud mode, with all computational workload being federated over the network to a remote 48-core machine through the CloudBees Accelerator cluster-architecture. The “48 agents, EADE” columns show the results when CloudBees Accelerator Developer Edition was being used on that single multi-core machine, with no distribution capability across remote machines. As you can see, significant performance improvement of both full and incremental builds in both setups!

Stay up to date

We'll never share your email address and you can opt out at any time, we promise.

Loading form...
Your ad blocker may be blocking functionality on this page. Please disable for an improved experience.