3 ms·

I tried out lambda to handle backend requests with a go executable. For a trivial request/response it took 100-300 ms for the first request and 3-100 ms for sub

by fwoqpdw 11y ago

I tried out lambda to handle backend requests with a go executable. For a trivial request/response it took 100-300 ms for the first request and 3-100 ms for subsequent requests. Using better hardware tended to help with the subsequent requests but there was still a lot of variance. This is too slow and has too much variance for my purposes, which is to respond to user events. Even if I added an optimization of having a go process which lives through multiple lambda calls, the first request latency sucks. (And I haven't verified that the optimization would work - unfortunately you can't use sockets which would make it simpler). TL;DR: pls support go (with consistent performance)

siscia 11y ago
What would be "fast" in your opinion ?
- fwoqpdw 11y ago
  Consistency is more of an issue with me than speed. That said, I would be happy if a trivial request (prints a short line of output) to a go handler would consistently be <10ms.
  - siscia 11y ago
    I am sorry but 10ms is really too short... You need to consider physical latency into the equation... If you live next to a Amazon data center you can hope to achieve such result, otherwise...
    - fwoqpdw 11y ago
      I'm talking about handler duration, doesn't include network latency. If you use lambda you can look at the durations in the logs... a trivial go handler often gets ~5ms if you're using good hardware (but sometimes jumps up to ~100ms)
      - siscia 11y ago
        Okok, now it makes senses :)