final long pid = ProcessHandle.current().pid();
            assertEquals("winhost:" + pid, systemHelper.getInstanceId());
        } finally {
            envMap.remove("COMPUTERNAME");
        }
    }

    @Test
    public void test_getInstanceId_uniquePerProcess() {
        // Verify that instanceId contains PID for process uniqueness

<font color="#A6E22E">INFO</font>:     Application startup complete.
```

</div>

////

这里唯一的新选项是 `--workers` 告诉 Uvicorn 启动 4 个工作进程。

您还可以看到它显示了每个进程的 **PID**，父进程（这是**进程管理器**）的 PID 为`27365`，每个工作进程的 PID 为：`27368`、`27369`， `27370`和`27367`。

## 部署概念 { #deployment-concepts }

在这里，您学习了如何使用多个**工作进程（workers）**来让应用程序的执行**并行化**，充分利用 CPU 的**多核性能**，并能够处理**更多的请求**。

          println("TLSv1.3 requires an external command run before first traffic is sent")
          println("Follow instructions at https://github.com/neykov/extract-tls-secrets for TLSv1.3")
          println("Pid: ${ProcessHandle.current().pid()}")

          Thread.sleep(10000)
        }
      }

      CommandLine -> {
        return ProcessBuilder(
          "tshark",
          "-l",
          "-V",
          "-o",

     * to ensure uniqueness across multiple JVMs on the same host.
     *
     * @return The instance ID.
     */
    public String getInstanceId() {
        final String targetName = ComponentUtil.getFessConfig().getSchedulerTargetName();
        final String hostname = getHostname();
        final long pid = ProcessHandle.current().pid();
        if (StringUtil.isNotBlank(targetName)) {

set APP_NAME=fess
set SEARCH_ENGINE_HOME=%FESS_HOME%/es

if NOT "%FESS_USE_GC_LOGGING%" == "" set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Xlog:gc*,gc+age=trace,safepoint:file=%FESS_HOME%/logs/gc-%APP_NAME%.log:utctime,pid,tags:filecount=5,filesize=64m

set FESS_CLASSPATH=%FESS_HOME%\lib\classes
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Dfess
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Des-foreground=yes

fi
if [ "x$FESS_CONTEXT_PATH" = "x" ]; then
  FESS_CONTEXT_PATH=/
fi
if [ "x$FESS_USE_GC_LOGGING" != "x" ]; then
  FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Xlog:gc*,gc+age=trace,safepoint:file=$FESS_LOG_PATH/gc-$APP_NAME.log:utctime,pid,tags:filecount=5,filesize=64m"
fi
FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dfess.home=$FESS_HOME"
FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dfess.context.path=$FESS_CONTEXT_PATH"
FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dfess.port=$FESS_PORT"

```

</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 }

<font color="#A6E22E">INFO</font>:     Application startup complete.
```

</div>

////

這裡唯一新增的選項是 `--workers`，告訴 Uvicorn 要啟動 4 個工作處理序。

你也會看到它顯示每個處理序的 **PID**，`27365` 是父處理序（這是**處理序管理器**），另外每個工作處理序各有一個：`27368`、`27369`、`27370`、`27367`。

## 部署概念 { #deployment-concepts }

你已經看到如何使用多個 **workers** 來將應用的執行進行**平行化**，善用 CPU 的**多核心**，並能服務**更多請求**。

<font color="#A6E22E">INFO</font>:     Application startup complete.
```

</div>

////

ここで唯一の新しいオプションは `--workers` で、Uvicornに4つのワーカープロセスを起動するように指示しています。

各プロセスの **PID** も表示されていて、親プロセス（これは**プロセスマネージャー**）が `27365`、各ワーカープロセスがそれぞれ `27368`、`27369`、`27370`、`27367` です。

## デプロイメントのコンセプト { #deployment-concepts }

		<packaging.fess.user>fess</packaging.fess.user>
		<packaging.fess.group>fess</packaging.fess.group>
		<packaging.fess.pid.dir>/var/run/fess</packaging.fess.pid.dir>
		<packaging.fess.systemd.dir>/usr/lib/systemd/system</packaging.fess.systemd.dir>
		<packaging.fess.systemd.sysctl.dir>/usr/lib/sysctl.d</packaging.fess.systemd.sysctl.dir>