If you check out the "task manager" or "system monitor" (or similar tools) in your operating system, you will be able to see many of those processes running.

And, for example, you will probably see that there are multiple processes running the same browser program (Firefox, Chrome, Edge, etc). They normally run one process per tab, plus some other extra processes.

```

</div>

////

The only new option here is `--workers` telling Uvicorn to start 4 worker processes.

You can also see that it shows the **PID** of each process, `27365` for the parent process (this is the **process manager**) and one for each worker process: `27368`, `27369`, `27370`, and `27367`.

## Deployment Concepts { #deployment-concepts }

A container is running as long as the **main process** (command or program) is running.

A container normally has a **single process**, but it's also possible to start subprocesses from the main process, and that way you will have **multiple processes** in the same container.

But it's not possible to have a running container without **at least one running process**. If the main process stops, the container stops.

## Decision

1. The Gradle distribution will never include a Java runtime.
   Instead, Gradle will leverage Java toolchains for the Daemon and worker processes.
2. The Gradle Daemon, Worker processes, and Tooling API client will continue to support running on different Java versions during a single Gradle invocation.
   The exact versions supported will be determined by the Gradle version.

        } catch (JobProcessingException e) {
            assertTrue(e.getMessage().contains("10 crawler processes are running"));
            assertTrue(e.getMessage().contains("Max processes are 5"));
        }
    }

    // Test execute method with no max process limit
    @Test
    public void test_execute_noMaxProcessLimit() {
        // Setup test
        crawlJob = new CrawlJob() {

        } catch (final Exception e) {
            if (logger.isDebugEnabled()) {
                logger.debug("Failed to process a ping request.", e);
            }
            writeJsonResponse(HttpServletResponse.SC_INTERNAL_SERVER_ERROR, e);
        }
    }

    /**
     * Processes a search request.
     * @param request The HTTP request.
     * @param response The HTTP response.

     * Client processes include the Tooling API client or the CLI client.
     */
    val client: Property<Boolean>

    /**
     * Declare that this Gradle module runs as part of the Gradle daemon.
     */
    val daemon: Property<Boolean>


    /**
     * Declare that this Gradle module runs as part of worker process.
     */
    val worker: Property<Boolean>

                    logger.debug("Failed to access UserInfo cache.", e);
                }
            }
        }
        return OptionalEntity.empty();
    }

    /**
     * Processes the search log queue.
     *
     * @param queue The search log queue.
     */
    protected void processSearchLogQueue(final Queue<SearchLog> queue) {

        try {
            this.threadPool = null;
            final RequestProcessor processor = new RequestProcessor(encoding, threshold);
            connect(processor, e -> {
                throw new CurlException("Failed to process a request.", e);
            });
            return processor.getResponse();
        } finally {
            this.threadPool = originalThreadPool;
        }
    }

如果你的遠端伺服器或虛擬機只有 3 GB RAM，嘗試載入超過 4 GB 的 RAM 就會出問題。🚨

### 多個行程 - 範例 { #multiple-processes-an-example }

在這個例子中，有一個「管理行程（Manager Process）」會啟動並控制兩個「工作行程（Worker Processes）」。

這個管理行程大概就是在 IP 的「連接埠」上監聽的那個。它會把所有通信轉發到各個工作行程。

那些工作行程才是實際執行你的應用的，它們會完成主要的計算，接收「請求」並回傳「回應」，也會把你放在變數中的東西載入 RAM。

<img src="/img/deployment/concepts/process-ram.drawio.svg">

當然，同一台機器上除了你的應用之外，通常也會有「其他行程」在執行。