a year ago
go-fiber deployment on railway slows it down 10X. same codebase deployed to ec2 instance with coolify is full-filling requests in 50ms - 100ms but when deployed to railway is taking upto 1.3secs to fulfil . both ec2 and railway deployments are in Singapore region. this is totally unacceptable that performance degrades simply by hosting on railway. its a go-fiber hello world app link- https://github.com/railwayapp-templates/fiber. First pic is of railway, second is of aws ec2+coolify nixpack deployment of same code of a railway template
update turning off metal anycast edge network and "downgrading" to Google Cloud edge network fixed it. but i am keeping this thread up as this is an legitimate bug.
25 Replies
second project same issue - 151e60da-a355-46cc-9ce3-b90228986b1c this is US West (California, USA) region
a year ago
Can you run a traceroute to 66.33.22.1 and show me the result please
traceroute to 66.33.22.1 (66.33.22.1), 64 hops max, 40 byte packets
1 [private IP] 3.224 ms 2.985 ms 3.448 ms
2 [ISP CGNAT] 6.369 ms 6.403 ms 10.907 ms
3 [ISP Network] 8.955 ms 6.735 ms 7.095 ms
4 [ISP Network] 6.933 ms 6.432 ms 7.003 ms
5 aes-static-125.34.144.59.airtel.in 8.516 ms 8.783 ms 9.652 ms
6 116.119.61.206 131.224 ms
116.119.49.38 132.402 ms
116.119.61.232 140.645 ms
7 mei-b5-link.ip.twelve99.net 133.527 ms 131.987 ms 131.531 ms
8 prs-bb2-link.ip.twelve99.net 149.900 ms 150.043 ms 150.723 ms
9 adm-bb2-link.ip.twelve99.net 162.951 ms
adm-bb1-link.ip.twelve99.net 160.864 ms 160.360 ms
10 adm-b12-link.ip.twelve99.net 155.448 ms 154.313 ms
adm-b12-link.ip.twelve99.net 166.424 ms
11 railwaycorp-ic-390073.ip.twelve99-cust.net 175.351 ms 166.573 ms 165.976 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
a year ago
Do you know how to use Wireshark by chance?
a year ago
That latency doesn’t look optimal but it also shouldn’t yield a 1.2s https response time
a year ago
No worries
a year ago
I’m going to try and fix our routing with Airtel this week
its not always 1s time it was between 400ms to 1.2 and with cloudflare 1.1.1.1 wrap it went to 8 secs max
a year ago
400ms makes sense for the worst case India->Amsterdam->Singapore round trip
a year ago
I’ll work on this and get back to you when to check again
a year ago
@Anosher Hello, could you confirm whether this is now fixed?
i m so sorry phineas i didnt see the msg. sorry to say it hasnt been fixed
😦
