---
schema_version: "1"
id: 5d7197a98c6d05b5c23b217dc215b746a8851e1ed2ae5ef7ecb020acb057f9e6
title: Multi-Join Report Performance
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-large-data-volumes-bp/guides/cce/ldv-deployments/ldv-deployments-case-studies-report-performance.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-large-data-volumes-bp/guide/ldv-deployments-case-studies-report-performance.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 34b88cac7e60647e132323f860bd8b3928a6760b6e44ffd189fb00980d328b5f
products:
  - Best Practices for Deployments with Large Data Volumes
  - Platform Developer Content
---

# Multi-Join Report Performance

## Situation

The customer created a report that used four related objects: Accounts (314,000), Sales Orders (769,000), Sales Details (2.3 million), and Account Ownership (1.2 million). The report had very little filtering and needed to be optimized.

## Solution

To optimize the report, the customer:

-   Added additional filters to make the query more selective and ensured that as many filters as possible were indexable
-   Reduced the amount of data in each object, whenever possible
-   Kept the Recycle Bin empty. Data in the Recycle Bin affects query performance.
-   Ensured that no complex sharing rules existed for the four related objects. Complex sharing rules can have a noticeable impact on performance.