}

        // Reserved (2 bytes)
        buffer[22] = 0x00;
        buffer[23] = 0x00;

        // TID (2 bytes)
        buffer[24] = 0x01;
        buffer[25] = 0x00;

        // PID (2 bytes)
        buffer[26] = 0x02;
        buffer[27] = 0x00;

        // UID (2 bytes)
        buffer[28] = 0x03;
        buffer[29] = 0x00;

        // MID (2 bytes)
        buffer[30] = 0x04;

    /** Open function fail if exists */
    int OPEN_FUNCTION_FAIL_IF_EXISTS = 0x0000;
    /** Open function overwrite if exists */
    int OPEN_FUNCTION_OVERWRITE_IF_EXISTS = 0x0020;

    /** Process ID */
    int PID = (int) (Math.random() * 65536d);

    /** Share level security */
    int SECURITY_SHARE = 0x00;
    /** User level security */
    int SECURITY_USER = 0x01;

    /** Command offset in SMB header */

            buf.append(ComponentUtil.getSystemHelper().getLogFilePath());
        }
        buf.append(File.separator);
        buf.append("gc-").append(getExecuteType()).append(".log");
        buf.append(":utctime,pid,tags:filecount=5,filesize=64m");
        return jvmOptions(buf.toString());
    }

    /**
     * Adds JVM options for this job execution.
     *
     * @param options the JVM options to add

            assertTrue(exception.getCause() instanceof NullPointerException);
        }

        @Test
        @DisplayName("Should work with different PID configuration")
        void testWithDifferentPidConfiguration() throws Exception {
            // Given
            Configuration config = mock(Configuration.class);
            when(config.getPid()).thenReturn(99999);

```

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

        testConfig.initDefaults();

        // Check random and time zone
        assertNotNull(testConfig.getRandom());
        assertNotNull(testConfig.getLocalTimezone());

        // Check PID is set
        assertTrue(testConfig.getPid() >= 0);
        assertTrue(testConfig.getPid() < 65536);

        // Check machine ID
        assertNotNull(testConfig.getMachineId());

		Type:      counterMetric,
	}
}

func getMinioProcessIOReadBytesMD() MetricDescription {
	return MetricDescription{
		Namespace: nodeMetricNamespace,
		Subsystem: ioSubsystem,
		Name:      readBytes,
		Help:      "Total bytes read by the process from the underlying storage system, /proc/[pid]/io read_bytes",
		Type:      counterMetric,
	}

	}

	if (!globalThis.process) {
		globalThis.process = {
			getuid() { return -1; },
			getgid() { return -1; },
			geteuid() { return -1; },
			getegid() { return -1; },
			getgroups() { throw enosys(); },
			pid: -1,
			ppid: -1,
			umask() { throw enosys(); },
			cwd() { throw enosys(); },
			chdir() { throw enosys(); },
		}
	}

	if (!globalThis.path) {
		globalThis.path = {
			resolve(...pathSegments) {