关于ClientConfig.setHeavyweight中Volt线程数量配置规则的技术问询

Great question—let’s unpack this clearly based on the ClientConfig JavaDoc and standard VoltDB client behavior.

First, let’s restate the key detail from the docs:

When setHeavyweight(true) is enabled, the client calculates a base value N as Runtime.coresAvailable / 2.

Here’s the critical clarification:

• N represents the number of threads allocated to each of the two separate thread pools:
  • The Volt Network thread pool gets N threads (these handle network I/O, connection management, and incoming responses)
  • The Volt Reaper thread pool also gets N threads (these handle cleanup tasks, timeout checks, and resource reclamation)

You won’t split N in half between the two pools—each pool gets the full N value derived from half your available cores.

Example to make it concrete #

If your system has 8 available CPU cores:

• N = 8 / 2 = 4
• Volt Network threads: 4
• Volt Reaper threads: 4

This design makes sense for heavyweight mode, which is optimized for high-throughput workloads. By dedicating a full N threads to each pool, the client ensures network operations and cleanup tasks don’t compete for resources, keeping both critical workflows running efficiently.

内容的提问来源于stack exchange，提问作者aamadeo