Optimize formula calculations in Base

2 min read
I. Performance diagnostics
If you find that your base lags when you filter, group, sort, or scroll or that formulas take a long time to calculate, you can use the Performance Diagnostics tool to troubleshoot and optimize the base.
Note: After upgrading to the new version of Base, the system will switch from browser-based computing to server-side computing. In this mode, tasks are processed on the cloud, so local computer resources are not used, leading to improved performance and a smoother user experience.
II. Term descriptions
  • Suboptimal formulas: Refers to formula calculations that take a long time, generally involving query functions like FILTER, COUNTIF and SUMIF.
  • FILTER, COUNTIF, and SUMIF functions: These are statistical functions in Base, which can filter data according to specified conditions and then perform summation, counts, and other calculations.
  • Binary operators: These include =, !=, <, >, <=, >=, &&, II, CONTAIN, and more.
  • Formula lag: Refers to the page lagging when you scroll or when performing actions such as filter, group, sort, and lookup on a formula field.
III. Common scenarios for suboptimal formulas
Scenario 1: Calculations are performed directly on CurrentValue.list in the conditions, and multiple variables are introduced.
Issue description
The FILTER formula is used to look for keywords in sales feedback. Formulas with performance risk have "keyword" variables. This fuzzy matching scans every row of the "Sales feedback" list, resulting in slow queries.
Contains performance risk
Sales feedback.FILTER(
CurrentValue.Feedback details.CONTAINTEXT(keywords)
).Feedback quantity.COUNTA()
No performance risk
Add keyword labels such as "Feedback label" to "Sales details" in the "Sales feedback" list, to reduce the number of variables.
Sales feedback.FILTER(
CurrentValue.Feedback label = Keywords
).Feedback quantity.COUNTA()
IV. Formula optimization
When the amount of data increases, the computing power used by suboptimal formulas will rise exponentially, slowing down the entire base. We recommend optimizing these formulas by doing some of the following:
Method 1: Filter for and correct suboptimal formulas.
  • Hover over the icon in the lower-right corner of a base and click Performance Diagnostics.
250px|700px|reset
  • In the Performance Diagnostics pane, filter for formulas with slow queries and long calculation, and optimize the formulas according to the prompts.
250px|700px|reset
Method 2: Follow the formats below as closely as possible when writing your formulas.
Formula format
Sales summary table.FILTER(
CurrentValue.List name Operator = / >= / <= / != List name/Constant &&
CurrentValue.List name Operator = / >= / <= / != List name/Constant &&
CurrentValue.List name Operator = / >= / <= / != List name/Constant
)
.Results
.LISTCOMBINE()
.SUM() / COUNTA() / UNIQUE()
Detailed example
Sales summary table.FILTER(CurrentValue.Salesperson = Salesperson && CurrentValue.Sales volume > 0).Sales volume.SUM()
Method 3: Consider using extensions for complex scenarios.
If you need to perform calculations on a large amount of data or if your calculations involve a lot of variables, consider using extensions instead. For details, see Use extensions in Base.
Method 4: Reduce the number of variables used in operations as much as possible.
Scenario description
You need to calculate the total sales volume for different members for different years.
Contains performance risk
Uses multiple variable lists:
List 1: Table.FILTER(CurrentValue.Year=2021&&CurrentValue.Member = Name).Sales volume. SUM()
List 2: Table.FILTER(CurrentValue.Year=2022&&CurrentValue.Member = Name).Sales volume.SUM()
No performance risk
Uses one variable list:
Table.FILTER(CurrentValue.Year=Year list&&CurrentValue.Member = Name).Sales volume.SUM()
250px|700px|reset
Written by: Lark Help Center
Updated on 2025-03-17
How satisfied are you with this content?
Thank you for your feedback!
Need more help? Please contact Support.
0
rangeDom