tree 1d973bbfd69cc52983f88374693fae4a5da505c5
parent 63f0b36e61864cc805f50618ac72f76440ba4b84
author ulfjack <ulfjack@google.com> 1580226457 -0800
committer Copybara-Service <copybara-worker@google.com> 1580226512 -0800

Use a ForkJoinPool for async include scanning

Previously, switching to a FJP was rolled back due to introducing a
performance regression in some cases. While I was unable to reproduce
the regression due to other changes in Bazel, this ties the switch to
the async include scanner flag. I have carefully benchmarked that, and I
think that switching to a FJP is required to roll out the async include
scanner.

PiperOrigin-RevId: 291931477