Currently, PubSub Subscriber creates multiple threads based on Runtime.availableProcessors(). This is a reasonable default but should be configurable, specifically when there are other competing threads pools, and also when running in Docker containers, where Runtime.availableProcessors() may not return the allocated CPUs (see https://bugs.openjdk.java.net/browse/JDK-6515172)
Currently, PubSub Subscriber creates multiple threads based on Runtime.availableProcessors(). This is a reasonable default but should be configurable, specifically when there are other competing threads pools, and also when running in Docker containers, where Runtime.availableProcessors() may not return the allocated CPUs (see https://bugs.openjdk.java.net/browse/JDK-6515172)