Pasting here the response @Kabirdas gave me via support because I think it could be useful to other users:
If you haven't already you might want to check out our docs on query runtimes as they give a bit of context as to what each of those categories means. In your case, I think this might be due to some latency in communicating with our backend. Our servers are located in the pacific northwest of the US, so to execute your query you'd need to
- Send the request from your browser to our backend servers
- Have our backend servers send the request to your DB
- Have your DB send the response to our backend
- Have our backend send the response to your browser
Since it looks like you're located pretty far from our servers steps 1) and 4) can add significant latency, and if your DB server is also located far away there will be more latency in steps 2) and 3).
For some users, this is a reason to consider using a self-hosted instance of Retool since that lets you control where the backend is hosted and can cut down on latency.
In my case I'm in Europe and my DB is in Europe, so that'd mean the data crossing the Atlantic 4x before I get a response (Europe -> US West -> Europe -> US West -> Europe).
A possible solution besides self-hosting Retool would be running a replica of my DB hosted in the US, but for now I'll leave it like it is now, not worth the hassle IMO.