> For the complete documentation index, see [llms.txt](https://docs.arcology.network/arcology-architecture-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcology.network/arcology-architecture-overview/scheduler.md).

# Scheduler

The scheduler is responsible for allocating transactions, making optimal transaction execution plans, and managing resources available based on the execution strategy.

## 1. Execution Plans

The scheduler first scans through all the transactions it has received from transaction pool service for their characteristics and then divides them into subsets called generations. The whole transaction execution process may comprise a number of generations. Smart contracts are presumed parallelizable until proven otherwise.

Different generations will be processed in a serial order. For better performance, the scheduler will try to put in as many parallelizable transactions as possible in a single generation. Each generation is further subdivided into multiple batches. Different transaction batches will be sent to different EUs for execution.

![generations](/files/RbJ3b9QqN3h1dBtX7y8H)

## 2. Conflict History

At the end of each block cycle, the scheduler will update its internal conflict database based on conflict information detected by the feedback from the Arbitrator. If two different smart contracts are found conflicting with another, the scheduler will avoid putting a them in a same generation in a future cycle.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.arcology.network/arcology-architecture-overview/scheduler.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.