> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/monitoring/datasets/partitions.md). # Partitions The **Partitions** tab provides insights into the top 100 largest partitions in the table, helping you analyze and manage data distribution effectively. Iceberg's schema evolution capabilities allow partition specifications to evolve over time. Partitions created using an older partition specification will no longer receive new data, but they remain visible in the list as long as they are retained in storage. These partitions are marked with an **Historical** icon to distinguish them.

View the metrics for the top 100 partitions comprising your Iceberg table.

For each partition, you can track the following statistics:

Metric	Description
Partition	The name of the partition.
Avg.File Size	The average size of data files within the partition.
Total Files	The total number of data files in the partition.
Uncompacted Files	The number of files in the partition that have not been compacted.
Partition Size	The current size of the partition.
Projected Partition Size	The projected size of the partition after compaction is complete.
Current Scan Overhead	The current request overhead by S3 API calls in order to fully scan the partition.
Projected Scan Overhead	The projected request overhead by S3 API calls to scan the partition after compaction is complete.

--- # 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, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/reference-1/monitoring/datasets/partitions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.