Will having tables in tables be less efficient than just variables?

I’m using profile service to store data. I want to clean up the table and make it readable for me by using tables inside tables/nested tables, but I saw a post somewhere and someone said that storing tables inside of tables is less efficient and just to add comments to make it readable. Is that true? If not I will use nested tables.

Like this: without nested tables
image

With nested tables:

Does anyone know if setting it up like the second picture will be less efficient, atleast somewhat noticeably? Much appreciated

You will have to add more code to adjust for the structure change, and if any data currently exists you will have to scrap it, which is why some say it is less efficient.

If you think that trade-off is good enough for readability though, go ahead. The performance difference is negligible in the end.

1 Like

Technically it will be slower since instead of doing a single lookup (tab[“key”]), you’re now doing two (tab[“key”][“key”]). However, computers are fast, and dictionary look ups are relatively fast operations themselves. So basically, the performance difference likely does exist, but it’s so incredibly small that you’re better off going with the more readable option.

1 Like

I use profileservice too and I use nested tables, don’t see any problem with coding or any delay

1 Like

Nested tables make it easier to organize

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.