Thank you. Yes, the early benchmarks definitely seem exciting! I'm working on a comprehensive benchmark with resource usage, latency reports, throughput and more (and benchmarking against more systems now).
Apart from your buzzword marketing, what features are actually available for use today? Most are "on the roadmap." Reminds me of Spacedrive which literally launched with a "nice UI" and no actual features that they advertise for.
Hi johnwoods - Tobie founder of SurrealDB here. We're updating our website so it's clearer, but in the meantime, the best page to see the current functionality is our features page https://surrealdb.com/features
We're also looking to improve our roadmap page soon, which will detail everything we're working on and planning to work on in the near term, and in the future!
That's a hell lot of buzzwords (GPT-3 trained with HN titles, eh?). Does "serverless" and "cloud-native" database together even make any sense? Idk, but I feel like these folks are doing too much pointless marketing when the core product literally just "borrows" code from other databases without any credit to them.
I think it's time we say "Stable Diffusion Powered Hyperfast Scalable Ultimate Cloud-Native Kubernetes Native Document Graph Relational NewNoSQL Database"
Enough of the buzzwords on HN, honestly. Also, NOT FOSS.
please note that I ran the bench with 30 threads with 1 connection per thread. you're not doing the same but doing 28 threads with 20 connections on each thread, effectively using 560 connections whereas I only used 30 connections. rerun the same with -t 30 and -c 1
if I'm doing my math right: redis is doing 99892 sets per sec, so 25X should be 2,497,300. the video however shows 1,023,030 which is more like 10X and NOT 25X
agree with your article entirely. the dragonfly benchmark seems far too artificial to be true and used in practice (given the expensive hardware). my tests were on a relatively cheaper box, and Skytable topped all the other systems.
From your own numbers, Dragonfly get ~3.6-4 times better perf than Redis, and better than keydb (which is “just” multhreaded redis-simplifying). That indicates pretty clearly to me that we’re not getting same-or even close performance-on existing hardware; and ultimately, if performance is that important, shouldn’t we be giving our applications every advantage they can get?
Looking forward to the benchmarks and 1.0!