Big app means some features won't work

Need help
1

I have an app with some of the DBs hitting 100k, most around 20-50K items.
In my app I already cannot use:
Optimize Application
Search logs within a desired period

– As the app is too big. –

Anybody has any insight:
When will bubble fix this so we can actually have access to bubble features?
Any nice workarounds apart - for browsing logs (I know I can make my own logs, but want to check things in the past).

1 Like
2

The log history is independent of DB size.

3

People have been saying as the app gets bigger or interval between ‘‘optimize application’’ gets longer higher the prob of it not working increases.

But that is not true in my case can you try issue_checker_off then click optimize ?

4

I do not believe the number of database entries (ie: amount of storage in use) is going to cause issue with the Optimize Application feature as that feature is more focused on your Bubble app JSON file which is larger as you add more to an app.

1 Like
5

Thanks! @boston85719
My app is pretty big I would say.

And I would check @emir.ozgun trick to make sure no stone is unturned.

6

This is affected by editor complexity, not database size.

This is known to be slow and not useful on large apps but you can try reducing the number of event types returned and narrowing the dates you’re searching for.

The way optimize app works roughly speaking is it goes through the entire app JSON and loads all elements/pages/reusables etc. You can see this by seeing the browser memory usage increase as it runs. It just crashes on large apps.

2 Likes
7

2 more questions then:

  1. Is there a way to look for an actions which creates a specific database thing?
    As I either see create a thing and I declare a string.
    Or there is a uses field - to look for actions that touches field - and this way I can later go for it.

  2. Is there a way to limit the search just for actions? As when I search for field, I usually get like 600 results where only actions actually interest me.

PS: I lov ya!

8

Uhh you could delete the data type and then it’ll get flagged in the issue checker (making sure you’ve enabled it in backend workflows)

1 Like
9

I was always afraid to delete data types/fields.

10

You can always restore them, it doesn’t affect the data in them.

1 Like
11

No it won’t. Deleted fields are not flagged because of the restore function. If they flagged them as red the restore function wouldn’t work properly.

Best way to search for field usage is the app search tool search by field.

Plus issue checker is broken, so even if deleting a field caused issue is issue checker you’d have to open every page, every reusable and backend workflows to make sure issue checker loads issues.

2 Likes
12

True my bad

13

Thanks for great input you guys. It’s sad how bubble did absolutely nothing about it in the last 2 years. Nothing regarding performance, nothing regarding logs and features break from too big apps.

14

This topic was automatically closed after 70 days. New replies are no longer allowed.