Improving your stack performance

Tips to improve your loading speed and performance of your stacks (databases) in Stackby

Improving the speed of your databases is largely dependant on how you’ve structured your databases.

Some of the best practices include:

  • Creating views instead of tables, to filter and hide information and let your team members get access to those views.
  • Delete any unused rows
  • Remove formulas, links, lookups or rollups that are redundant and non essential.
  • Reduce API usage or insert pauses between API calls.

Don’t structure your database like below:

  • Creating multiple tables instead of views for months, statuses, collaborators or more.
  • Create multiple tables that have same fields but are not using linked rows.
  • Creating tables that summarize information in other tables without using linked rows in the same base.
  • Creating multiple tables in the same stack, tracking different stages of projects.
  • Creating individual tables for different time-frequencies (weeks, months, quarters).
  • Creating individual tables for categories (products, projects, types of events).
  • Creating individual tables for each collaborator.

In short, use views in your tables properly, remove unnecessary redundant information, link across unique tables and summarize information to measure key metrics.

Hope this helps!