--- slug: /manage/partitions title: Partitions description: Partitions speed the search process by allowing an admin to filter a subset of the log messages in an index. canonical: https://www.sumologic.com/help/docs/manage/partitions/ --- import Iframe from 'react-iframe'; import useBaseUrl from '@docusaurus/useBaseUrl'; Creating a partition enhances search performance by narrowing down the search scope to a smaller subset of messages. Use the Partitions page to set up and manage partitions. [**New UI**](/docs/get-started/sumo-logic-ui/). To access the Partitions page, in the main Sumo Logic menu select **Data Management**, and then under **Logs** select **Partitions**. You can also click the **Go To...** menu at the top of the screen and select **Partitions**. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the Partitions page, in the main Sumo Logic menu select **Manage Data > Logs > Partitions**. A partition stores your data in an index separate from the rest of your account's data so you can [optimize searches](../../search/optimize-search-performance.md), [manage variable retention](manage-indexes-variable-retention.md), and specify certain [data to forward to S3 or GCS](../data-forwarding/forward-data-from-sumologic.md). :::note Data stored in a partition is not stored anywhere else.  ::: import TerraformLink from '../../reuse/terraform-link.md'; :::tip You can use Terraform to provide a partition with the [`sumologic_partition`](https://registry.terraform.io/providers/SumoLogic/sumologic/latest/docs/resources/partition) resource. ::: ## About partitions Partitions route your data to an index becoming a separate subset of data in your account. Creating smaller and separate subsets of data is central to search optimization. When you run a search against an index, results are returned more quickly and efficiently because the search runs against a smaller data set. After routing messages to a partition, you can reference it in your search by using the field `_index` with the partition's name. See [Optimize Your Search with Partitions](/docs/search/optimize-search-partitions) for details. Partitions ingest your messages in real time. They differ from scheduled views in that partitions don’t backfill with aggregate data. They begin building a non-aggregate index from the time the partition is created and index only the data moving forward. Scheduled views backfill with aggregate data, meaning that all data that extends back to the start date of the view query is added to the view. You define the data that will reside in a partition by defining a routing expression, which is similar to a log query, but with certain restrictions in terms of the operators you can include. Each partition's routing expression is applied to all messages as they are ingested to Sumo Logic. If a message matches the partition’s routing expression, it is added to the partition. ## Micro Lesson: Partitions basics :::training Micro Lesson