Optimizing Performance of Your App

This feature is available to app admins (app builders) on the Enterprise-level plan. You can use this feature to do either of the following:

  • Automatically find and apply performance optimizations to your app

  • Preview possible optimizations to your app (simulation mode)

Note that the first option makes changes to your app. In accordance with our backup and restore policies, you can reach out to our technical support team for help reverting your app. To profile the performance of specific actions in your app, you can use the performance analyzer.

To begin:

  1. In your app, click the settings icon , then App management.

  2. Under Manage App Structure, click Optimize performance. The Performance Optimizer page appears.

  3. Click Start optimization. A dialog box appears.

  4. Select Find and apply performance improvements... or Preview possible optimizations without applying them.

  5. Click Start. It can take some time for the process to complete and while it does, performance can be impacted. To see new optimizations as they are found or applied, refresh this page. Once the process is complete, you’ll see a “Done” entry.

If you would like to apply possible optimizations, run the steps above again, but in Step 4, select Find and apply performance improvements...

Note that for all optimizations, Quickbase verifies data integrity by ensuring that the number of records returned by a query or filter match pre and post optimization(s).

Things we optimize

Quickbase finds and optimizes on the build and platform levels.


The following refers to optimizations that Quickbase can automatically make to patterns configured by builders and users in an app. These changes are visible in their respective areas.

  • Report filtering: For all reports with active and recent usage, Quickbase attempts to find the most optimal ordering of filters for that report. Optimizations to a specific report benefit only where that report is directly used (such as viewing it standalone, referenced in an API call, or embedded on a dashboard).

  • Summary field filtering: For all summary fields with filtering applied, Quickbase attempts to find the most optimal ordering of filters for when that summary field is used as a single returned column in a query. This isolates it to ensure Quickbase is optimizing the performance of that field. Optimizations to a summary field benefit each place that it is referenced, which may include, but is not limited to: calculations, display columns, filters, permissions, etc.

  • Permissions filtering: For all roles with custom access configured for an app, Quickbase attempts to find the most optimal ordering of filters for a given role/table combination when processing a List All report that only returns the Record ID#. Optimizations to permissions benefit nearly all actions on a table for any users in the affected role.

  • Remove obsolete choices: In many field types, Quickbase maintains a possible list of options for the field (such as multiple choice and certain key fields). As builders change field types and change other properties, these maintained lists are kept for restoration purposes. Performance optimization clears obsolete choices after a period of unuse so that builders do not need to clear them manually.


The following refer to optimizations and tuning that cannot be applied to the entire Quickbase platform as they may adversely affect certain apps while benefiting others.

  • Thread optimizations: On each report with recent usage, Quickbase identifies the most efficient thread architecture to run that report for and save the configuration. This is not visible or configurable by builders.