Consider "thread pool size" over "thread pool depth"

[binkley]

https://github.com/rufusraghunath/kelda/blob/68687436769b458a6a65520f9f797b862fa51b6f/src/kelda/Kelda.ts#L10

The word "depth" many not be as clear as "size" in context.

Alternatively, perhaps "thread pool queue depth" is meant here?

[rufusraghunath]

It's the number of Threads/Workers you're allowed to have at any one time. The queue only gets used to buffer Jobs when the threadPoolDepth is exceeded. You can see it used to populate the Threads when ThreadPool is initialized here.

I chose "depth" over "size" because it evokes "pool" for me. Is "size" more standard in the Java world?

[binkley]

Yes, I think you'll find "size" is the more common word choice to describe this.

• Thread pools --> "size"
• Queues --> "depth"

In Javaland, the thinking runs along these lines (also true in Linux kernel land):

• Threads --> # of potential concurrent code executions
• Queues --> # of pending executions