# An app with 130 columns? Is it feasible? **URL:** https://community.glideapps.com/t/an-app-with-130-columns-is-it-feasible/49326 **Category:** Ask for Help **Created:** [September 14, 2022, 7:57pm UTC](https://community.glideapps.com/t/an-app-with-130-columns-is-it-feasible/49326 "2022-09-14T19:57:08Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager) #### Post date: [September 14, 2022, 8:24pm UTC](https://community.glideapps.com/t/an-app-with-130-columns-is-it-feasible/49326/2 "2022-09-14T20:24:32Z")
Generally I think you are fine. I think there are several apps out there with well over 100 columns. I believe there are extenuating circumstances where you may have performance issues, but you won’t know until you try. In reality I think that pales in comparison to the kinds of things @Darren_Murphy has done. I would actually read through the entire thread below to get a better idea of observations that a few of us have had. > [@App Performance (\>10k row apps)](https://community.glideapps.com/t/app-performance-10k-row-apps/43276/21): > > I think technically yes, but as I suggested it’s probably negligible in terms of impact on performance. I guess a much bigger factor would be what you subsequently do with those relations. For example, let’s say you create a relation to a table with 5k rows. And then you add a series of Lookup columns to fetch values via that relation. Then you might use the values from those lookups in a template, and then use that template to create another relation, and so on… All of this is going to create … --- _[View the full topic](https://community.glideapps.com/t/an-app-with-130-columns-is-it-feasible/49326)._