Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

About 6months ago we had to leave now v1 because of bad TTFB times compared to Heroku (me in Europe and server in USA east - now gave 800-900ms TTFB with massive variance > 2s vs Heroku constant 250ms TTFB). We left because of those bad TTFB times and an unresponsive support from my point of view, once they left slack in favour of spectrum [1, 2] it was impossible to get a response. I had left some detailed tests. (Spectrum is hosted on now I think which has currently a 2s TTFB for me in Spain).

I really wanted to use now because the developer experience is so great but the TTFB made itunusable for us to host customer facing services and lack of support response made it hard to stay.

[1] https://spectrum.chat/zeit/now/slow-response-times-for-node-... [2] https://spectrum.chat/zeit/now/latency-discrepancy-between-n...



For those who needed to look it up like me, it stands for "Time to First Byte". #SavedYouAGoogle :)


> We left because of those bad TTFB times and an unresponsive support from

Had strictly the same issue with zeit.

Performance is horrible.

I also remember seing a somewhat similar issue about latency opened on GitHub[0].

They randomly closed it without giving any explanations or further details.

That's great support for sure !

[0] https://github.com/zeit/now-cli/issues/592


From my experience, every single time a company/product moves to Spectrum, the quality of support drops significantly, both from staff and the community. I really don't understand why people like it, and why they were bought by GitHub.


This has been improved massively with Now 2.0. Feel free to do any benchmarks on it!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: