* Continuously processes crawled documents from the data service, transforms them,
     * and updates the search index until crawling is finished and all documents are processed.
     *
     * <p>The method performs the following operations in a loop:
     * <ul>
     * <li>Retrieves access results from the data service</li>
     * <li>Processes each document through transformers</li>

* mount (verb): montar
* statement (as in code statement): statement (do not translate to "declaración" or "sentencia")
* worker process: worker process (do not translate to "proceso trabajador" or "proceso de trabajo")
* worker processes: worker processes (do not translate to "procesos trabajadores" or "procesos de trabajo")
* worker: worker (do not translate to "trabajador")
* load balancer: load balancer (do not translate to "balanceador de carga")

 * referenced in HTML documents. This generator extracts images from HTML content
 * and processes them to create thumbnail images based on configured dimensions
 * and format settings.
 *
 * <p>The generator validates image MIME types, processes image data through
 * ImageIO operations, and applies scaling and cropping to generate thumbnails
 * that meet the specified size requirements.</p>
 *

                }
            }
        }
    }

    /**
     * Processes Google on/off comment directives in the node.
     *
     * @param node the node to process
     * @param flag the flag indicating whether content should be included
     * @return the processed node
     */
    protected Node processGoogleOffOn(final Node node, final ValueHolder<Boolean> flag) {

This is still true.

So, to be able to have **multiple processes** at the same time, there has to be a **single process listening on a port** that then transmits the communication to each worker process in some way.

### Memory per Process { #memory-per-process }

        }
    }

    /**
     * Processes and normalizes a document title.
     * Applies text normalization using configured space characters and returns
     * a clean title suitable for indexing.
     *
     * @param responseData the response data from crawling (not currently used)
     * @param title the raw title text to process
     * @param dataMap additional data map (not currently used)

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.

```

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

            flush();
        }
        return (long) ids.length;
    };

    /**
     * Processes the score boosting.
     * @return The number of processed documents.
     */
    public abstract long process();

    /**
     * Enables this score booster.
     */
    protected void enable() {

     * @param fessConfig the Fess configuration
     * @param entity the thumbnail queue entity to process
     */
    protected void process(final FessConfig fessConfig, final ThumbnailQueue entity) {
        final SystemHelper systemHelper = ComponentUtil.getSystemHelper();
        systemHelper.calibrateCpuLoad();

        if (logger.isDebugEnabled()) {
            logger.debug("Processing thumbnail: {}", entity);
        }