Performance
Loading performance is key to streamlining your operations. Here are a few steps we recommend to take to ensure your Forest is optimized.
1. Show only Smart fields you absolutely need
As you can see in the Loading time benchmark below, Smart fields can be quite costly in terms of loading performance. Limiting them to those you absolutely need is key.
2. Reduce the number of records per page
3. Reduce the number of fields displayed
You can hide some fields in your table view; this will not prevent you from seeing them in the record details view.
4. Show only Relationship fields you absolutely need
Relationship fields are links to other collection records within your table view:
Having Relationship fields can decrease your performance, especially if your tables have a lot of records. Therefore you should display only those you actually need and use!
As Forest Admin generates SQL queries to fetch your data, creating indexes can improve the query response time. Indexing is a large subject but here a few tips about indexing:
Index the Primary and Unique Key Columns Make sure that the primary key for each table and any unique key columns that exist are indexed.
Index the Foreign Key Columns Foreign key columns should be indexed if they are used intensively in Smart fields. In the table below, you can see how drastically it reduces the loading time of the page.
Note that using too many indexes on a table can be counter-productive and decrease performance.
Below is the outcome of a performance test on page load time of the Table view.
It highlights the importance of using indexes and limiting the number of columns and lines.
The above benchmark was done using a SQL database.
Please note that NoSQL databases (MongoDB,..) don't perform as well as SQL databases when used with relationships. The "1 relationship" column above would show higher loading time for a NoSQL database.
