3 ms·

I'm impressed by the low latency, great job sir

• gregsadetsky 4y ago
  Indeed, it's very well done. Each isochrone is loaded from a static server/CDN -- for example https://chronotrains-eu.vercel.app/api/isochrones/7100002 https://chronotrains-eu.vercel.app/api/isochrones/7100002 -- and that bit of vector map data is then rendered using the mapbox gl/js frontend. Great work
  • Kon-Peki 4y ago
    Unfortunately it's been hugged to death. I wonder if it loads the entire set of isochrones when you open the page, given how incredibly responsive it is. I tried to share it with someone who would really enjoy it, but alas, no luck at all.
    • gregsadetsky 4y ago
      Aye, it is indeed down, that's sad. The isochrones are loaded over the network on mouse hover. I thought that scheme would keep working and remain fast since the loaded vector data is completely static. I guess the /api/isochrones/<id> url does point to some server-side code which couldn't keep up, unfortunately. Actually, Vercel is returning "This Serverless Function was rate limited." and a 429 code i.e. too many requests. So it's more of a "hitting the limits of the Vercel plan" problem than anything.