4 ms·
SereneDB's C++ search engine is the fastest on search benchmarks
- Uniplace 7mo agoGreat results! Refreshing to see a project that actually went the extra mile and built the core search engine in C++ from scratch, unlike most similar projects that just wrap an existing library.
- malandin 7mo agoThank you for your feedback! We have long thought that the space was missing an alternative.
- deleted 7mo ago[deleted]
- deleted 7mo ago[deleted]
- scammer228 7mo ago[dead]
- mkornaukhov 7mo ago[flagged]
- leonid_y 7mo agoI can't wait to apply this base to my real-time AI forecasting solutions!
- malandin 7mo agoHi Leonid! More than happy to talk about this! Find me on social networks by by nickname.
- akorchak 7mo agoVery impressive numbers! I def would love now to learn more about the algo behind these results
- gnusi 7mo agoThanks! There some articles on our blog. Check it out!
- savbelyakov 7mo ago[dead]
- stevemk14ebr 7mo agoTesting on 5GB of data fully resident in ram is a terrible comparison. Things get hard when you're in the hundreds of gigabytes or more.
- malandin 7mo agoThanks a lot for your comment! We agree that a dataset as small as 5 GB may sound strange but it was a conscious decision. Check out our blog post to read more about the methodology of this benchmark itself. https://blog.serenedb.com/search-benchmark-game-overview https://blog.serenedb.com/search-benchmark-game-overview
- deleted 7mo ago[deleted]
- MBkkt 7mo agoTLDR It's not our choice, but it's meaningful. Because this 5GB is single data segment and literally what you will have in Elastic/etc when you have overall TBs of data. See https://www.elastic.co/docs/deploy-manage/production-guidance/optimize-performance/size-shards https://www.elastic.co/docs/deploy-manage/production-guidanc... (single shard is one Lucene index that contains multiple data segments)