#railway
3 posts tagged railway. · All tags
- Failing to Reproduce It Locally Did Not Mean There Was No Bug After the move to Railway, the web frontend climbed from 226MB to 833MB in a straight line over 26 hours. It was not render load, and the sibling service on the same stack was fine. I hammered it with 3,000 requests on my Mac, could not reproduce it, and wrote down "not reproducible by request volume." Then I measured again inside a container and got 388KB per request. The platform had been hiding the signal
- I Left Cloudflare to Get Faster I asked whether to move the whole backend to Cloudflare. Before moving, I measured, and a page that never calls the backend and a static PNG were both the same 0.47 seconds. The free plan was killing 1 in 5 requests, and the conclusion was the exact opposite direction
- When the Constraint Changed From Money to Quota, I Needed a Queue I shut down self-hosted GPU serving and switched to the subscription CLI, and the shared layer I had nailed down in April as "don't build it," this time I built.