Hello, I have a table that is being populated by an API endpoint (using FillArray), is there a maximum number of rows that a table can have?
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 16th August 2023
Hi Carys,
There isn’t really a hard limit.
However, if the table contains a large number of rows (e.g. more than 2000) it could cause problems for the client systems to load and present all data.
In such cases, it’s better to add the partial option to your table, so only the first x number of rows (1000 by default) are loaded in the UI.
Floris Cockaerts [SLC] [DevOps Advocate] Posted new comment 17th August 2023
Hi
Have a look at the Data Handling page.
There you will find some basic guidelines with very large tables:
- Performing sets (FillArray):
- Try to stay below 20 000 cells in 1 set, except if the content of a cell is a 20 MB string or something equally large, in which case you should split up more.
- Avoid setting more than 1000 rows at a time. If your table is larger than 1000 rows, use multiple sets per 1000 to improve performance.
Andries Deklerck [SLC] [DevOps Member] Answered question 14th August 2023
Just to put some numbers out there, although there are plenty of performance and memory complications when going to 100K rows and above, there is currently a limit at 2^32-1 where the software will not be able to correctly store and retrieve data in its data structures, even when running the 64-bit version of SLProtocol.