504 time-outs and slow addition of queries

[limpid patio]

Hi there,

Since this morning, after having upgraded to a newer version as well (1.9.7), we've encountered some performance problems.

• The dashboard / overview itself loads really fast
• Loading large individual apps is either insanely slow or has become impossible (504 timeouts)
• The problem started appearing after adding new queries to an app.
• Adding new queries (from existing data sources) in new, empty, blank apps, is very slow (sometimes up to 20 seconds). It does not really matter which source.

We've been looking into server logs, but there are no relevant errors there. The timeout setting is really substantial already, and appsmith ran perfectly fine on this server size before.

Any ideas how to solve this?

[scarlet agate]

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Team Appsmith

[limpid patio]

We've restored a Mongo backup from before, and the app runs fine now - still weird the issue happened with a minor addition.

[scarlet agate]

Hey @limpid patio,

Thanks for reaching out to us about this. Will you be able to share the
performance profiles for this action? Here is our guide -
Slow app loads -
https://www.notion.so/appsmith/Profiling-app-load-time-3a0986a001d049bcb422eb42776f6f19
Slow action trigger -
https://www.notion.so/appsmith/Profiling-an-action-in-chrome-dev-tools-9db5cae117f1446fbf67251ad7bb55f9
[https://www.notion.so/appsmith/Profiling-an-action-in-chrome-dev-tools-9db5cae117f1446fbf67251ad7bb55f9]

[limpid patio]

Ha @scarlet agate, thanks for your reply! Since the db restore the issue is resolved, but may we encounter the issue again, we'll share a performance profile.

[scarlet agate]

Thanks for your continuous support and patience. We hope your issue is resolved
now.

Let us know how did we do?
https://survey.frontapp.com/v2/09a400bf433bc9676d67/6aaf085f50821d3d4b2c31c06301787c

[limpid patio]

We re-encounter the problem with larger apps, especially if they have larger javascript objects.

The problem reappears when modifying Js objects, especially when adding properties, and sometimes when adding a new query.

Subsequently, it affects the whole app, slowing down other apps as well.

I can run the client based profiler from notion, but the error message we get is a 504 which is usually server related.

The nginx error logs for the container do not show anything, and we already increased nginx timeouts. Seems that appsmith also has its own timeout of 20 seconds - not sure where to adjust that.

From the appsmith logs, the following is logged only when loading an app / editing an app;

userEmail=[redacted], sessionId=[redacted], thread=lettuce-epollEventLoop-6-1, requestId=[redacted] - Going to fetch applicationPageDTO for applicationId: null, pageId: 63ef37d9db5b59733c95916d, branchName: master, mode: EDIT

The given page will return a 504

[scarlet agate]

Please help us with the following information for debugging this issue:

1. Send us the full server logs to help us investigate the issue. You can grab
   the logs by running docker logs -f appsmith. Or you could follow the steps
   from this guide on how to get the
   logs

2. Send us the performance profiles as per this guide -
   Slow app loads -
   https://www.notion.so/appsmith/Profiling-app-load-time-3a0986a001d049bcb422eb42776f6f19
   [https://www.notion.so/appsmith/Profiling-app-load-time-3a0986a001d049bcb422eb42776f6f19]
   Slow action trigger -
   https://www.notion.so/appsmith/Profiling-an-action-in-chrome-dev-tools-9db5cae117f1446fbf67251ad7bb55f9
   [https://www.notion.so/appsmith/Profiling-an-action-in-chrome-dev-tools-9db5cae117f1446fbf67251ad7bb55f9]

3. If possible, share the app with us. Add [email protected]
   [[email protected]] as a Developer and send us the link to it.

[limpid patio]

Thanks, we skipped client based profiling because the error code was server related and server side logs from appsmith were quite empty...

The error is related to the git integration, at a certain moment the app breaks and the whole thing goes sideways. Since we removed the git integration from our apps, they work fine and 504s haven't happened.