Java 用于多线程服务器的 CachedThreadPool 与 FixedThreadPool

Java CachedThreadPool vs FixedThreadPool for multithreaded server

我有一个服务器,它不断监听客户端连接,并在每次客户端连接时创建一个新线程来处理该客户端的 I/O。现在,我有多个 类 实现 Runnable 并且在 运行 方法中有一个 while 循环,该循环一直持续到客户端关闭。我创建了一个新的 Thread 对象并将 运行nable 传递给该对象。我很确定还有其他更有效的方法可以做到这一点。我应该切换到 cachedThreadPool 或 fixedThreadPool 还是其他东西?

如果未定义客户端大小,我建议使用 Executors#cachedThreadPool

文档 Executors#cachedThreadPool:

* Creates a thread pool that creates new threads as needed, but
* will reuse previously constructed threads when they are
* available.  These pools will typically improve the performance
* of programs that execute many short-lived asynchronous tasks.
* Calls to {@code execute} will reuse previously constructed
* threads if available. If no existing thread is available, a new
* thread will be created and added to the pool. Threads that have
* not been used for sixty seconds are terminated and removed from
* the cache. Thus, a pool that remains idle for long enough will
* not consume any resources.

文档 Executors#fixedThreadPool:

* Creates a thread pool that reuses a fixed number of threads
* operating off a shared unbounded queue.  At any point, at most
* {@code nThreads} threads will be active processing tasks.
* If additional tasks are submitted when all threads are active,
* they will wait in the queue until a thread is available.

因此,如果您不确定是否确实需要 5 个线程,则不应使用 Executors#fixedThreadPool