9 ms·

Sure, I will.

• pier25 5y ago
  Thanks for the merge. As you pointed in the PR you're only measuring the latency of the first query so it will have no effect in the benchmark. I'm guessing the "current request" latency will improve though, no? I have to say the latencies you're getting are much higher that I've experienced with Fauna. Obviously it's expected for a KV database to be faster, but I'd be surprised to get more than 100ms of 50th percentile.
  • noahfschr 5y ago
    Current request latency is also the read latency (from lambda function -> db). I should have been more clear on that.
    • pier25 5y ago
      Still, almost a second of total latency (50th percentile) is super high. I'd love to do the same test from Cloudflare Workers instead of AWS Lambda. Could you please DM on Twitter to discuss this? https://twitter.com/PierB https://twitter.com/PierB Edit: I just saw this comment by Evan from Fauna which explains why the latency could be so high: https://news.ycombinator.com/item?id=26806541 https://news.ycombinator.com/item?id=26806541