3 months ago
So I have a simple db set up and I've been noticing long response times for simple queries. It's not a large db in terms of data or schema definitions.
I used Drizzle Studio Gateway to run sql queries and see response times, images are attached.
Don't know if I'm doing something wrong or if it's something on Railway's side. Any suggestions for improvement would be great.
Attachments
3 Replies
3 months ago
Hey,
We have just pushed a significant improvement to the TCP Proxy. I'm not saying it's the magic bullet here, but I just wanted to ask if you now see any improvements before we debug this further.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Might have a 20-100ms impact but if you're service is connecting over a public network it'll be margins slower then over the private network.
Would suggest switching to the Internal Network!
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
@error I moved to a private network for Drizzle Studio but that didn't help much.
@brody It's still some issues. For the first query it took a second, but for the subsequent queries it took ~140ms.
Then I tried another table selecting only the ID column and that took ~450ms.
Screenshots are attached.
Attachments