> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings.md).

# General instance and processing settings

The following configuration settings are for the general instance setup and processing.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Set the number of macine learning and RoBERTa workers</strong></td><td>Used to enable parallel processing in Textual.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/textual-config-ml-roberta-worker-count.md">Configuring the number of workers for machine learning and RoBERTa</a></td></tr><tr><td><strong>Configure timeouts</strong></td><td>End a session automatically based on inactivity or overall session length.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/inactivity-timeout-max-session-length.md">Setting an inactivity timeout and maximum session length</a></td></tr><tr><td><strong>Configure processing and parallelism</strong></td><td>Configure how Textual jobs are processed.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/config-processing-parallelism.md">Configuring processing and parallelism</a></td></tr><tr><td><strong>Configure log format</strong></td><td>Set the format to use for Textual logs.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/textual-config-log-format.md">Configuring the format of Textual logs</a></td></tr><tr><td><strong>Set a custom certificate</strong></td><td>Provide a custom certificate to use for https traffic.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/textual-custom-certificate.md">Setting a custom certificate</a></td></tr><tr><td><strong>Configure custom AWS endpoints</strong></td><td>Set custom endpoint URLs for calls to AWS services.</td><td></td><td><a href="/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/custom-aws-endpoint-urls.md">Configuring endpoint URLs for calls to AWS</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.