---
title: "Configuring publishing performance"
slug: "configuring-publishing-performance"
abstract: "Describes how you control performance when you publish to Experience Edge."
---
# Configuring publishing performance

When you publish to Experience Edge, resource consumption can peak at many of the stages the process goes through. The connector module uses APIs from the [Task Parallel Library (TPL)](https://docs.microsoft.com/en-us/dotnet/standard/parallel-programming/task-parallel-library-tpl) such as *Data parallelism* and *Dataflow* to maximize performance, providing a simple way to control and scale the performance based on the available processors.

This topic describes two aspects of performance you can control in the configuration.

<details>
<summary><h2>Controlling the publishing manifest creation performance</h2></summary>

Publishing manifest creation involves iterating over all the items identified as being published and searching for dynamic dependencies for each, using the Solr index created for this. The manifest is processed in parallel, and the index queries are batched against a group of items to reduce the index round trips.

To control the publishing manifest creation performance, configure the following:

- The `ExperienceEdge.MaxManifestExpandThreadCount` setting controls the maximum number of parallel threads used to expand the manifest.
- The `ExperienceEdge.MaxManifestSearchQueryTermsCount` setting controls the maximum number of items used in a single search query.

</details>

<details>
<summary><h2>Controlling the publishing manifest export performance</h2></summary>

The connector performs several operations on all manifest items to export the manifest. Network latency significantly impacts the performance of these operations. Some repeated local operations (loading item data from the database, generating JSS layout for a page, and generating the GQL schema for the database) also impact performance.

The connector uses a [TPL Dataflow](https://docs.microsoft.com/en-us/dotnet/standard/parallel-programming/dataflow-task-parallel-library) for concurrency in all export operations where it is possible.

To control the publishing manifest export performance, configure the following:

- The `ExperienceEdge.ExportEntitiesBufferSize` setting controls the size of the export pipeline buffer.
- The `ExperienceEdge.MaxExportEntitiesThreadCount` setting controls the maximum number of parallel threads used to export the items in the manifest.

While entities are uploaded individually, entity publishing events are grouped and sent in batches. To control the batch size for publishing events:

- Specify the value of the `ExperienceEdge.ExportPublishEventsBatchSize` setting.

    > [!note]
    > When you specify a value higher than the value of `ExperienceEdge.ExportEntitiesBufferSize`, the value of the latter is used.

</details>