"application/vnd.handheld-entertainment+xml",
				"application/vnd.hbci",
				"application/vnd.hcl-bireports",
				"application/vnd.hhe.lesson-player",
				"application/vnd.hp-hpgl",
				"application/vnd.hp-hpid",
				"application/vnd.hp-hps",
				"application/vnd.hp-jlyt",
				"application/vnd.hp-pcl",
				"application/vnd.hp-pclxl",
				"application/vnd.httphone",
				"application/vnd.hydrostatix.sof-data",

    <glob pattern="*.les"/>
  </mime-type>
  <mime-type type="application/vnd.hp-hpgl">
    <glob pattern="*.hpgl"/>
  </mime-type>
  <mime-type type="application/vnd.hp-hpid">
    <glob pattern="*.hpid"/>
  </mime-type>
  <mime-type type="application/vnd.hp-hps">
    <glob pattern="*.hps"/>
  </mime-type>
  <mime-type type="application/vnd.hp-jlyt">
    <glob pattern="*.jlt"/>

 * to be locked or unlocked, including the process ID, offset, and length.
 *
 * @author mbechler
 */
public class LockingAndXRange implements Encodable, Decodable {

    private final boolean largeFile;
    private int pid;
    private long byteOffset;
    private long lengthInBytes;

    /**
     * Constructs a LockingAndXRange with large file support.
     *
     * @param largeFile whether to use large file support (64-bit offsets)

        decodedSmb.decode(buffer, 0);

        assertEquals(smb.command, decodedSmb.command);
        assertEquals(smb.mid, decodedSmb.mid);
        assertEquals(smb.pid, decodedSmb.pid);
        assertEquals(smb.tid, decodedSmb.tid);
        assertEquals(smb.uid, decodedSmb.uid);
        assertEquals(smb.flags2, decodedSmb.flags2);
        assertEquals(smb.wordCount, decodedSmb.wordCount);

        lock.encode(new byte[20], 0); // initialise fields by encoding to set pid etc (though not needed)
        setField(lock, "pid", 123);
        setField(lock, "byteOffset", 100L);
        setField(lock, "lengthInBytes", 200L);
        LockingAndXRange unlock = new LockingAndXRange(false);
        setField(unlock, "pid", 456);
        setField(unlock, "byteOffset", 300L);
        setField(unlock, "lengthInBytes", 400L);

    }

    /**
     * Gets the process identifier
     * @return the pid
     */
    public final int getPid() {
        return this.pid;
    }

    /**
     * Sets the process identifier
     * @param pid
     *            the pid to set
     */
    public final void setPid(final int pid) {
        this.pid = pid;
    }

    /**
     * Gets the user identifier
     * @return the uid

    SigningDigest digest = null;
    ServerMessageBlock response;

    ServerMessageBlock() {
        flags = (byte) (FLAGS_PATH_NAMES_CASELESS | FLAGS_PATH_NAMES_CANONICALIZED);
        pid = PID;
        batchLevel = 0;
    }

    void reset() {
        flags = (byte) (FLAGS_PATH_NAMES_CASELESS | FLAGS_PATH_NAMES_CANONICALIZED);
        flags2 = 0;
        errorCode = 0;
        received = false;

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

</div>

////

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

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

## 部署概念

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

从上面的部署概念列表来看，使用worker主要有助于**复制**部分，并对**重新启动**有一点帮助，但您仍然需要照顾其他部分：

| `minio_node_io_read_bytes`                 | Total bytes read by the process from the underlying storage system, /proc/[pid]/io read_bytes.                  |
| `minio_node_io_wchar_bytes`                | Total bytes written by the process to the underlying storage system including page cache, /proc/[pid]/io wchar. |

            andx.command = andxCommand;
            andx.errorCode = errorCode;
            andx.flags = flags;
            andx.flags2 = flags2;
            andx.tid = tid;
            andx.pid = pid;
            andx.uid = uid;
            andx.mid = mid;
            andx.useUnicode = useUnicode;

            if (andx instanceof AndXServerMessageBlock) {