Excess contention in ExecutorService

When profiling a client with 200K active RPCs, there is a point of contention on the Executor. Each RPC gets its own SerializingExecutor, which executes work on an underlying executor. Currently, that executor is ThreadPoolExecutor in almost all cases, which itself has a BlockingQueue. That queue is heavily contended showing up at _minutes_ of wasted time:

```
141.17mins 79.41% 79.41% 141.22mins 79.44% java.util.concurrent.LinkedBlockingQueue.offer LinkedBlockingQueue.java
36.51mins 20.54% 99.95% 36.52mins 20.54% java.util.concurrent.LinkedBlockingQueue.take LinkedBlockingQueue.java
```

An idea to fix this is to have some sort of striping executor in order to prevent this contention from happening.

Comienza examinando la ruta de SerializingExecutor y ThreadPoolExecutor descrita en el issue, incluida la contención de BlockingQueue mostrada por el perfil. El alcance consiste en definir y evaluar un enfoque de striping-executor para la carga de trabajo de 200K-RPC; el issue no especifica archivos, pruebas ni un criterio de finalización más concreto.

Escrito por el modelo de indexación a partir del texto del issue.