Access to this feature can change based on your Quickbase plan. Learn more about feature availability and plans in Quickbase capabilities.
The Performance Optimizer looks at patterns in how data is viewed in the app. Then, it finds the most optimal order of filtering for:
- Reports
- Summary fields
- Permissions
How the Performance Optimizer works
Optimizing the filtering in these areas leads to improved app performance. While the Performance Optimizer looks at filters, it will also remove obsolete choices from fields.
The following table shows more details about each of these.
| Area |
What's evaluated |
Where you'll see improved performance |
| Report filtering |
Reports with active and recent usage |
Anywhere that report is directly used (such as viewing it standalone, referenced in an API call, or embedded on a dashboard) |
| Summary field filtering |
Summary fields with filtering applied. Quickbase finds the most optimal ordering of filters for cases 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. |
Each place the summary field is referenced, like calculations, display columns, filters, permissions, etc. |
| Permissions filtering |
Roles with customized access to an app. Quickbase finds the most optimal ordering of filters for a given role/table combination when processing a List All report that only returns the Record ID#.
|
Nearly all actions on a table for any users in the affected role. |
| Obsolete choices |
Any field types (multiple choice and certain key fields) that maintain a list of possible field values for restoration purposes. Quickbase clears obsolete choices that have not been used for a certain amount of time. |
Any reports that include these fields. |
In addition to performing optimizations on reports, summary fields, and permissions, the Performance Optimizer will also look for special thread optimizations that can apply to your app.
Threads are coding objects that make up the back-end of Quickbase. Threads allow multiple process to run at once (like filters and queries on reports).
Thread optimizations have to be applied on a case-by-case basis. To apply a thread optimization, Quickbase looks at each report with recent usage. Then it identifies the most efficient way to architect the threads making that report work.
This fine-tuning can only be performed by the Performance Optimizer; it is not visible to app builders.
How to run the Performance Optimizer
You must be an app admin to access the Performance Optimizer.
-
Select App settings in the sidebar.
-
Click App management.
-
Under Manage App Structure, click Performance management.
-
The page opens to Performance Insights. Click the Performance Optimizer tab.
-
Click Start optimization. A dialog box appears.
-
Select Find and apply performance improvements or Preview possible optimizations without applying them.
-
Click Start.
It can take some time for the Performance Optimizer to complete its process, and you may notice some impact to app performance while it is running.
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 chose to preview possible optimizations, follow the steps above again to apply the performance improvements.
For all optimizations, Quickbase verifies no data is lost by making sure that the number of records returned by a filter or query match pre and post optimization(s).
If you select Find and apply performance improvements, Quickbase makes changes to your app. If you need to revert the changes, reach out to our technical support team. They will help in accordance with our backup and restore policies.