# Glide Big Tables | Bad performance **URL:** \ **Category:** Ask for Help\ **Tags:** big-tables\ **Created:** [November 21, 2024, 9:30am UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092 "2024-11-21T09:30:08Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\ **Post date:** [November 25, 2024, 5:47pm UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/6 "2024-11-25T17:47:36Z")
These tips can be useful for you: > [@App Performance Tips & Tricks: SPEED!](https://community.glideapps.com/t/app-performance-tips-tricks-speed/73139/17): > > Tabs can have a benefit in some cases because some tables may not run computed columns until necessary. Less content on a page can have a benefit as there is less to render. I really don’t think this has an effect. I think the largest speed issues will depend on how your data is structured. Any computed columns that rely on the values of computed columns in multiple other rows will have a large impact. Ask yourself this question…will displaying something on a screen require multiple rel… I was going to suggest 2-3 ideas but the Jeff’s tips already covered all this I hope it helps you! --- _[View the full topic](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092)._