### One Process per Container { #one-process-per-container }

In this type of scenario, you probably would want to have **a single (Uvicorn) process per container**, as you would already be handling replication at the cluster level.

    protected MavenContext createContext(InvokerRequest invokerRequest) {
        // TODO: in a moment Maven stop pushing user properties to system properties (and maybe something more)
        // and allow multiple instances per JVM, this may become a pool? derive key based in invokerRequest?
        MavenContext result = residentContext.computeIfAbsent(
                "resident",
                k -> new MavenContext(invokerRequest, false, (MavenOptions)

                            toList()
                        )
                    )
                );

            changelogsByVersionByTypeByArea.put(version, changelogsByTypeByArea);
        });

        // Sort per-area changelogs by their summary text. Assumes that the underlying list is sortable
        changelogsByVersionByTypeByArea.forEach(
            (_version, byVersion) -> byVersion.forEach(

* References

 * {{{./cli.html}CLI options}},

 * {{{./logging.html}logging API}}.

 * since 3.3.1 (see {{{/docs/3.3.1/release-notes.html#Core_Extensions}3.3.1 release notes}} for more details),
   per project settings can be defined by files in <<<.mvn/>>> directory:

   * <<<.mvn/jvm.config>>> containing jvm options,

   * <<<.mvn/maven.config>>> containing Maven command-line parameter,

        repository.</description>
      <cliOptions>
        <cliOption>
          <key>-Dmaven.repo.local=/path/to/local/repo</key>
          <value>Override the local repository location on a per-build basis.</value>
        </cliOption>
      </cliOptions>
    </expression>
    <expression>
      <syntax>reactorProjects</syntax>
      <description>This is the current list of projects being built by

  private static final class PerThreadQueuedDispatcher extends Dispatcher {

    // This dispatcher matches the original dispatch behavior of EventBus.

    /** Per-thread queue of events to dispatch. */
    @SuppressWarnings("ThreadLocalUsage") // Each Dispatcher needs its own state.
    private final ThreadLocal<Queue<Event>> queue =
        new ThreadLocal<Queue<Event>>() {

MinIO is built ground up on the cloud-native premise. With features like erasure-coding, distributed and shared setup, it focuses only on storage and does it very well. While, it can be scaled by just replicating MinIO instances per tenant via an orchestration platform.

> In a cloud-native environment, scalability is not a function of the application but the orchestration platform.

     */
    @Required
    public String queryId;

    /**
     * The search query string for error page display.
     */
    public String q;

    /**
     * The number of search results per page for error page display.
     */
    public String num;

    /**
     * The sort criteria for search results for error page display.
     */
    public String sort;

    /**

			Optional:    true,
			Type:        "int",
		},
		config.HelpKV{
			Key:         DriveWorkers,
			Description: `the number of workers per drive to heal a new disk replacement` + defaultHelpPostfix(DriveWorkers),
			Optional:    true,
			Type:        "int",
		},
	}

drives, some applications with high concurrency might require MinIO cluster to be tuned such that to avoid random I/O on the drives. The way to convert high concurrent I/O into a sequential I/O is by reducing the number of concurrent operations allowed per cluster. This allows MinIO cluster to be operationally resilient to such workloads, while also making sure the drives are at optimal efficiency and responsive.

Example: Limit a MinIO cluster to accept at max 1600 simultaneous S3 API requests...