Relation between druid.server.http.numThreads and druid.broker.http.numConnections

Hi,
I want to understand how changing the following properties for broker and historical nodes helps and what these actually mean.
historical node can be tuned by adjusting following values:
druid.server.http.numThreads - Number of threads for HTTP requests.
historical node can be tuned by adjusting following values:
druid.server.http.numThreads - Number of threads for HTTP requests
druid.broker.http.numConnections - Size of connection pool for the Broker to connect to Historical and real-time processes. If there are more queries than this number that all need to speak to the same process, then they will queue up.
For the broker node and for the historical node what purpose does druid.server.http.numThreads serves? Does these parameters affect concurrent query processing in any way?

For broker node should druid.broker.http.numConnections be more than/less than/equal to druid.server.http.numThreads ?

Thanks,

Prathamesh

Here are some guidelines for connection pool sizing, processing threads and buffers https://github.com/apache/incubator-druid/blob/master/docs/content/operations/basic-cluster-tuning.md

Thanks,

Sashi