40 ms·
We really wanted to like Render, but the performance just wasn't there for us when doing a bunch of load testing against Heroku, which is a shame. Hoping they c
by domh 4y ago
We really wanted to like Render, but the performance just wasn't there for us when doing a bunch of load testing against Heroku, which is a shame. Hoping they can make it better in the coming months/years cos we really liked the product.
- MobileVet 4y agoInteresting. Could you share more about the types of loads you were testing with? Our tests for simple JavaScript endpoints with a MongoDB call to be just as fast or faster on Render. Additionally the availability of far more tiers of cpu/ram meant we could see the same performance for half the cost.
- domh 4y agoNode.js + mongodb, definitely some not-so-performant pages with a few more db lookups than probably necessary. We also spun up a new Atlas cluster in the same region to rule out the cross data center latency.
- MobileVet 4y agoThat sounds very similar. We also spun up a Mongo instance in us-east-2 and the performance was fantastic. Round trip from the server to the mongo instance was super low and comparable to the Heroku / Mongo times on us-east-1 Bummer you had a different experience.
- anurag 4y agoHi Dom! After more evaluation, we think your experience was a Virginia vs Ohio problem. Once we have Virginia set up (along with a few other things our teams talked about) I'd love for y'all to give us another shot.
- MobileVet 4y agoHey Anurag Any chance you can share the timeline on the VA region roll out?
- Adorism80 4y agoHey, I’m sure Anurag has a more definitive answer here, but I saw him mention on Twitter that it’s on the calendar for this summer.
- domh 4y agoThat sounds great! Really hoping we can, we're still yet to find an alternative.
- tylerhannan 4y agoIs there something different in the configuration that would cause the impact of Virginia vs. Ohio?