# 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:** 6\ **Page:** 1
**Author:** ![Faris\_Ben\_Saad](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/faris_ben_saad/32/69822_2.png) [@Faris\_Ben\_Saad](https://community.glideapps.com/u/Faris_Ben_Saad)\ **Post date:** [November 21, 2024, 9:30am UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/1 "2024-11-21T09:30:08Z")
Hey Gliders, Just some **Context** : - We had an Airtable-only Backend for our application so far. - The application is very feature-rich and has several queries (we’re already optimizing on that) - despite the application being a little slow in the Glide Dev portal it’s still fast in the Live portal for our clients - because of several sync issues related to Airtable we decided to switch to Glide Big Tables for new features **Problem** : - After implementing a new feature with 2 new Glide Big Tables (currently with about 30-300 rows) our whole application got very very very slow in the Glide Dev. Environment. - And for the first time ever the new feature that is based on Glide Big Tables is so god damn slow in the Live portal that you can barely use it. **Details on the new feature** : - It’s a table with about 10 columns displaying rows from an Airtable T1 - Each entity in T1 (= WorkerPlacements) has a 1:1 relation to an entity in a Glide Big Table T2 (SignatureRequests) - The table has 2 columns with one action button each to do sth. with an entity from T2, e.g. For each Worker the user can create a SignatureRequest - For the action buttons a Worker references to it’s SignatureRequest - If one action button is clicked it takes 20-50 seconds until another button can be clicked and everything feels very slow. **Question** : - Did anyone have experiences with slow Glide Big Tables so far and can give some advice? ---
**Author:** ![slscustom.ru](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/slscustom.ru/32/77336_2.png) [@slscustom.ru](https://community.glideapps.com/u/slscustom.ru)\ **Post date:** [November 21, 2024, 10:03am UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/2 "2024-11-21T10:03:23Z")
Hi! Firstly try to check Performance Analysis to determine which computed column take a long time to calculate ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/d/6da034245e2108a11cc894c0b26fe323c7d5f804.png) ---
**Author:** ![Faris\_Ben\_Saad](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/faris_ben_saad/32/69822_2.png) [@Faris\_Ben\_Saad](https://community.glideapps.com/u/Faris_Ben_Saad)\ **Post date:** [November 22, 2024, 4:58pm UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/3 "2024-11-22T16:58:13Z")
![Screenshot 2024-11-22 at 16.47.32](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/2/92f7e5e55f57eb11dd641bc4dc5cf7a685769ea0.png) So, I tried to clean everything up. Only kept the very crucial things and that’s what I found: 1. The 2 Glide Big Tables seem to have sufficient performance (marked green 🟢) 2. The look up fields in the table Placements T1 have a bad performance (marked red 🔴) - but relative to other columns the performance should still be good enough. 3. Despite that the application using the Glide Big Tables didn’t get faster. It’s so slow we even have clients that complained about the performance. I already tried it with _single value_ instead of _lookup_ but that didn’t change anything. Are Glide Big Tables not supposed to be used in other tables? ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [November 23, 2024, 12:53am UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/4 "2024-11-23T00:53:24Z")
How are those lookups configured? I assume it’s on top of a relation/query? ---
**Author:** ![Faris\_Ben\_Saad](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/faris_ben_saad/32/69822_2.png) [@Faris\_Ben\_Saad](https://community.glideapps.com/u/Faris_Ben_Saad)\ **Post date:** [November 25, 2024, 7:56am UTC](https://community.glideapps.com/t/glide-big-tables-bad-performance/78092/5 "2024-11-25T07:56:30Z")
Hi @ThinhDinh, yes they’re are configured on top of this conditional relation: ![Screenshot 2024-11-25 at 08.55.33](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/0/50bee008764f2aac46ffcee73a555e15eda07b1b.png) ---
**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!