3 ms·

I'm getting around 250ms response times for https://legiblenews.com https://legiblenews.com from the UK after multiple refreshes. 500ms occasionally. I feel li

• bradgessler 4y ago
  You're not imaging things: I'm running a bit hot right now from HN load (https://s3.amazonaws.com/bradgessler/Eu1cKE24dpKjTkqNcK3qPqH3mwwXirAlOJiZXN9Sd4nSOdWtU4N6Ir3NB96h0WGkXo3NzEghEzUl8dYOOwSgFhcRQlXMuy6WfruS.png https://s3.amazonaws.com/bradgessler/Eu1cKE24dpKjTkqNcK3qPqH...) w/ ~170ms for the 99th percentile. It doesn't help that I'm running this on Heroku, which isn't known for being super fast. I'll probably deploy this to https://fly.io/ https://fly.io/ in the future to a few different geographies around the world so that I can bring latency down for the entire planet while saving myself a boatload in hosting costs.
  • bestinterest 4y ago
    That is interesting to see. I wonder if fly.io/heroku matters for the servers however. Caching the webpage with a CDN sounds like most bang for buck right? One request is slow at the start of the day for the news (maybe its a user requesting far away the main server worst case) but every subsequent request is served from close to user CDN. (Not 100% if thats how it works in practice) Speaking out loud here just to see if server location matters if you have a good CDN setup or something I'm missing which would make requests need to hit the main server.
  • synu 4y ago
    Why not generate it as a static site?