page.user.max.fetch.size=1000
# Maximum number of role records to fetch per page.
page.role.max.fetch.size=1000
# Maximum number of group records to fetch per page.
page.group.max.fetch.size=1000
# Maximum number of crawling info parameters to fetch per page.
page.crawling.info.param.max.fetch.size=100
# Maximum number of crawling info records to fetch per page.
page.crawling.info.max.fetch.size=1000

     * Get the value for the key 'rate.limit.requests.per.window'. <br>
     * The value is, e.g. 100 <br>
     * comment: Maximum number of requests allowed per window.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getRateLimitRequestsPerWindow();

    /**
     * Get the value for the key 'rate.limit.requests.per.window' as {@link Integer}. <br>

```

It could even be an infinite stream, where you keep sending data.

## JSON Lines { #json-lines }

In these cases, it's common to send "**JSON Lines**", which is a format where you send one JSON object per line.

A response would have a content type of `application/jsonl` (instead of `application/json`) and the body would be something like:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}

     * Indexes documents from a query log reader asynchronously.
     *
     * @param ctx The content indexing context
     * @param queryLogReader The query log reader
     * @param docPerReq The number of documents to process per request
     * @param requestInterval The interval between requests
     * @return A Promise that will be resolved with the SuggestIndexResponse
     */

Let's imagine that you have some **machine learning models** that you want to use to handle requests. 🤖

The same models are shared among requests, so, it's not one model per request, or one per user or something similar.

Let's imagine that loading the model can **take quite some time**, because it has to read a lot of **data from disk**. So you don't want to do it for every request.

 * <li>{@link #indexFromQueryLog(QueryLog[])} - Index from multiple query logs.</li>
 * <li>{@link #indexFromQueryLog(QueryLogReader, int, long)} - Index from query log reader with specified document per request and request interval.</li>
 * <li>{@link #indexFromDocument(Map[])} - Index from an array of documents.</li>
 * <li>{@link #indexFromSearchWord(String, String[], String[], String[], int, String[])} - Index from search word.</li>

### 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.

*.threaddump
# ps output for cleaning up leaking Java processes
*.psoutput

# oh-my-zsh gradle plugin
.gradletasknamecache

# Added GE support maven support to the maven build in .teamcity, per the GE docs, this dir is NOT to be committed
.teamcity/.mvn/.develocity/
/discoclient.properties

# Ignore local configuration files for asdf, allowing the JDK to be configured for project (https://asdf-vm.com)

 *       when using Executors.
 * </ol>
 *
 * <p><b>Other notes</b>
 *
 * <ul>
 *   <li>Usually, there is one testcase method per JSR166 method covering "normal" operation, and
 *       then as many exception-testing methods as there are exceptions the method can throw.
 *       Sometimes there are multiple tests per JSR166 method when the different "normal" behaviors

If one of your dependencies is declared multiple times for the same *path operation*, for example, multiple dependencies have a common sub-dependency, **FastAPI** will know to call that sub-dependency only once per request.