24 days ago
Something like:
DELETE FROM waiting_users WHERE socket_id = ? AND language = ?which takes 1ms on my local docker postgresql instance, is taking around 12 seconds (yes, SECONDS) on my PostgreSQL instance on railway. Both the app and the sql instance are at the same zone so i doubt its a network issue.
The primary key on the table is (socket_id, language), so in fact a simple delete by primary key cant be this slow. The waiting_users table IS partitioned by country (if that matters).
Please let me know if this is the expected SQL performance around here, because even tho im on the $5 plan to testing things, i think 12 seconds for a delete by primary key is unacceptable.
Thanks.
// Diego
5 Replies
24 days ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
24 days ago
Hi there, 12s is not the expected SQL performance — we are working on a fix for this but it may take some time to implement.
In the interim, we're happy to move you back to the Cloud machines (which are dead cold as we moved to shut them down)
Please let us know
Status changed to Awaiting User Response Railway • 24 days ago
23 days ago
Hi there, thanks for the response, i already removed / reworked the little stuff that was using postgresql into redis (it was due anyway), so this is not an issue (at least for me) anymore, thanks for your quick response tho.
// DIego
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
Gotchya. Will close this one out and if it returns don't hesitate to re-open!
Status changed to Awaiting User Response Railway • 23 days ago
Status changed to Solved jake • 23 days ago
5 days ago
🛠️ The ticket Performance issue with disk operations on metal has been marked as todo.