| commit | 0f4995615fc2dec3185c422b5fc1272bd0c8541a | [log] [tgz] |
|---|---|---|
| author | Nathan Harmata <nharmata@google.com> | Fri Aug 28 16:59:10 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon Aug 31 19:09:27 2015 +0000 |
| tree | 30e75a30ac644ec79df94ea9a62310106f8b8621 | |
| parent | 5d83e0f0db359c9133b058034e936bbad5604dd2 [diff] |
In GlobVisitor, use a ConcurrentHashSet and sort the results at the end rather than use a synchronized TreeSet that maintains the result in sorted order. Consider M adds to the set resulting in N unique elements (so M >= N). The old approach was O(MlogN) and the new approach is O(M + NlogN) and has less lock contention; the time spent holding the lock is O(N) vs O(MlogN) - and actually ought to be small in practice because of the internal striping in CHS. -- MOS_MIGRATED_REVID=101784791
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.