> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/mailscheduler/configuration/one-click/advanced-settings.md).
# Advanced settings
### Memory limit
If you get messages in the log like 'Allowed memory size of xxx bytes exhausted', you can fix these issues by increasing the memory limit in the advanced settings.
### Queue workers
Mailscheduler uses queues and jobs to send your emails for you at a scheduled time. One **Task** consists of multiple **Jobs**, and each of the jobs are handled by a different queue, which has by default one or multiple workers on it.
To increase MailScheduler performance, it is possible to increase the number of queue workers. Each worker will use around 150MB of RAM, and will also have an impact on your CPU, so make sure that you have enough for the amount of workers that you would like.
Please also keep the following limits in mind:
**Tableau Queue workers** multiplied with the Tableau Concurrency in the [General settings](/mailscheduler/configuration/general-settings.md) should **not** be greater than 20, unless your Tableau Server specifically allows more concurrent connections than this.
**Mail Queue** workers should be an amount below the maximum that your specific SMTP server supports without impacting other users on the SMTP server. If you are using **Microsoft Graph,** you can at most use **four** concurrent connections for the same mailbox.
You can see the default settings for the workers below:
{% hint style="info" %}
If you are experiencing issues with your MailScheduler installation slowing down, we recommend setting these settings back to their initial values
{% endhint %}
---
# 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.infotopics.com/mailscheduler/configuration/one-click/advanced-settings.md?ask=&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.
