noahfschr
Joined 5 years ago
Karma
29
Submissions
19
Member since
Apr 6
Recent submissions
Comment · 5 years ago
Comment · 5 years ago
I have commented this section and redeployed the code.
See the Fauna endpoint: https://71q1jyiise.execute-api.us-west-1.amazonaws.com/dev/f...
See the code: https://github.com/upstash/latency-comparison/blob/master/ne...
Comment · 5 years ago
Current request latency is also the read latency (from lambda function -> db). I should have been more clear on that.
Comment · 5 years ago
Upstash has two consistency modes. Eventual consistency and Strong consistency. Please see: https://docs.upstash.com/overall/consistency
In my code, Upstash database was eventually consistent. Similarly the index in the FaunaDB was not serialized.
But both of those should not affect the latency numbers in the histogram because those numbers are all read latency.
Comment · 5 years ago
I will be happy if someone from Fauna team helps me to improve my code.
https://github.com/upstash/latency-comparison
Upstash is not non-durable. It is based on multitier storage (memory + EBS) implementing Redis API. In a few weeks, I will add upstash premium which replicates data to multiple zones, to the benchmark app.
In the blog post, I mentioned the qualities where Fauna is stronger than the others: https://blog.upstash.com/latency-comparison#why-is-faunadb-s...
If you mean deleting Faunadb internal events, I do not know how to do. Can you guide me?