bazel-compile-commands-extractor icon indicating copy to clipboard operation
bazel-compile-commands-extractor copied to clipboard

Published 20 hours ago • verified publisher icon hedronvision

Use ProcessPoolExecutor instead of ThreadPoolExecutor.

Open ManishPatelKodiak opened this issue 5 months ago • 0 comments

With the ThreadPoolExecutor, it was observed that the compile commands extractor was effectively running single threaded for substantial periods of time, most likely due to the GIL. CPU utilization was only about one core. Using a ProcessPoolExecutor to work around the GIL seems to provide a substantial performance benefit - it was about 6x faster in a test run.

ManishPatelKodiak avatar May 20 '25 19:05 ManishPatelKodiak