Question about backend query time in retool

CleanShot 2023-03-18 at 15.35.57@2x
retool-SaaS <-> fly-postgresql-lax server

CleanShot 2023-03-18 at 15.39.44@2x
retool-SaaS <-> fly-postgresql-nrt server

We are currently using postgresql server via fly.io on nrt and lax.
The current service area is South Korea.

It is used as Retool SaaS, and the difference in 'execute resource time' when nrt and lax are connected respectively seems to be faster in the place connected to lax. This is the part that makes sense when I read the documentation that the Retool SaaS server is located in the US.

Anyway, the important part is, when connecting the two databases, the final time after query lookup in Retool seems to be similar in the end. I wonder how this can be improved.

Hi @Will_Heo! To make sure I’m following along correctly, you’re looking to improve the frontend post-processing time of your queries?

Also, these docs might be relevant here :slight_smile:

1 Like