---
title: "Formula queries and performance"
slug: "formula-queries-and-performance"
updated: 2026-04-29T17:03:22Z
published: 2026-04-29T17:03:22Z
canonical: "help.quickbase.com/formula-queries-and-performance"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Formula queries and performance

The following guidelines will help you avoid errors and performance issues when using formula queries.

## To help performance

- Do not filter, sort, or group reports based on formula query fields This avoids additional processing time and helps to optimize your apps as they grow.
- Use formula queries with complex logic in fields on tables, rather than as [report formulas](/v1/docs/using-a-report-formula)
- Do not make formula query fields searchable unless absolutely necessary

## Performance checks

When you create a formula query, or run one in a report or via API, Quickbase checks to see if it will have high performance impact.

If the performance impact is determined to be too high, an error message will prevent you from saving the formula until you've made adjustments.

### Suggested adjustments

- Eliminate the most records in the first comparison string to improve query speed
- Use manual input fields rather than derived fields like summary or formula fields
- Use exact matches when possible to build your filter criteria Using "is equal to" as your matching operator will be faster than using "contains"

If these suggestions do not resolve the issue, use the [performance analyzer](/v1/docs/analyzing-performance-of-apps) and [other performance tools](/v1/docs/improving-performance-and-scaling-apps) to find more ways to optimize your app.