- Studio Build: 4.0 Beta 3
- Version of Gradle Plugin: 3.6.0
- Version of Gradle: 6.1.1
- Version of Java: 1.8.0_242
- OS: Linux

Android Gradle plugin task class `DexArchiveBuilderTask` has [`numberOfBuckets`](https://android.googlesource.com/platform/tools/base/+/studio-master-dev/build-system/gradle-core/src/main/java/com/android/build/gradle/internal/tasks/DexArchiveBuilderTask.kt#118) input property with default value `Math.max(Runtime.getRuntime().availableProcessors() / 2, 1)` (see [in code](https://android.googlesource.com/platform/tools/base/+/studio-master-dev/build-system/gradle-core/src/main/java/com/android/build/gradle/internal/tasks/DexArchiveBuilderTask.kt#118)).

Usually developer machines and CI runners have different number of CPU cores (even CI runners between could have it different). This prevents usage of this task cache as it quite often produces cache misses.

Could you consider different approach to `numberOfBuckets` input property, so it will not introduce remote cache misses?

Current workaround is to get minimal available cpu cores on developers machines and CI runners and set it to `android.dexingNumberOfBuckets` in `gradle.properties`, though this is not a reliable approach and slows down dexing step.

Issue 152293185