# When is a glide app "too big"? **URL:** \ **Category:** Ask for Help\ **Created:** [November 16, 2021, 5:50am UTC](https://community.glideapps.com/t/when-is-a-glide-app-too-big/34581 "2021-11-16T05:50:34Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Roldy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/roldy/32/36068_2.png) [@Roldy](https://community.glideapps.com/u/Roldy)\ **Post date:** [November 16, 2021, 7:20am UTC](https://community.glideapps.com/t/when-is-a-glide-app-too-big/34581/7 "2021-11-16T07:20:16Z")
My latest experience that has brought benefits in terms of overall performance of the APP was to minimize the use of relations between GT tables and GS tables especially when used to search for data which is then used as the basis for a computed column. Or, even worse, for creating a new relation. This completely solved the ghost lines issue I reported a few months ago > [@Ghost rows (Sometimes they come back!)](https://community.glideapps.com/t/ghost-rows-sometimes-they-come-back/25483/): > > How to solve the problem of ghost rows that occasionally return to the list after they have been deleted, or after they are no longer part of the multiple relation that feeds the list. They come back occasionally and then they go away after some seconds… This not only happens in the Glide Builder but also in the devices where the APP is installed. It seems like a refresh problem … What is the logic? It seems to me that this happens: the APP updates the data locally and the row disappear th… and nowadays, I reduce relations as much as possible between GTs data as well. In other words, when possible, I replicate data in multiple tables instead of accessing them by relations. From my point of view, this fully confirms @Darren_Murphy 's thesis, which is that the problem is not the amount of static data contained in the tables. --- _[View the full topic](https://community.glideapps.com/t/when-is-a-glide-app-too-big/34581)._