Discovered some more issues.
As I stated above, I have a classic app on a legacy plan that I duplicated into a Starter team so I begin the process of rebuilding as a new app. It’s a slow process due to some of the above mentioned issues and I’m still over the row limit for a starter plan but it allows more data to be accessible so I can at least build my screens without most of the data being truncated.
Two things I noticed:
- Up until yesterday, the team folder contained the original classic app and the new app version…both of which share the same google sheet data source. Under usage I noticed that I was using 6.3Gb. Didn’t think much about it at the time. Yesterday I duplicated the new app to strip it down as a separate app for a very specific use case and noticed my data usage went to over 9Gb of usage. As I understand it, I believe I’m only using around 3Gb of actual Glide storage, but now it’s showing as tripled the amount because I have 3 apps that all share the same data source (and same urls to the same files). This doesn’t seem right as it should only be counting the same files once per team. Not multiple times.
- The other issue has been ongoing for years, but it seems like it usually works itself out after a couple of weeks. Like I said, I duplicated the new version of my app as another new app and stripped out most everything out of the app. The app SHOULD only be using a fraction of the amount of rows as Glide says they don’t count rows in unused tables. That’s not the case here. It’s still counting all rows, even in tables the app isn’t using. It’s counting something like 9600 rows while the app is only using tables that account for maybe 500 to 1000 rows tops. I’ve seen this a handful of times in the past, but usually after a week or two it seems like Glide will reanalyze, recount, and only look at used rows. It’s just not clear how these row counts work sometimes.