+972 52-548-6969
Working on Voron…
time to read 1 min | 53 words
This took a bit less than what I expected, but…
And yes, it works. And this is running on Ubuntu.
And no, it isn’t ready.
FUTURE POSTS
- Comparing DiskANN in SQL Server & HNSW in RavenDB - 9 hours from now
There are posts all the way to May 26, 2025
RECENT SERIES
-
RavenDB News
(2):
02 May 2025 - May 2025 -
Recording
(15):
30 Apr 2025 - Practical AI Integration with RavenDB -
Production Postmortem
(52):
07 Apr 2025 - The race condition in the interlock -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration -
RavenDB 7.1
(6):
18 Mar 2025 - One IO Ring to rule them all
RECENT COMMENTS
-
By Oren Eini on Scaling HNSW in RavenDB: Optimizing for inadequate hardware
-
By Scooletz on Scaling HNSW in RavenDB: Optimizing for inadequate hardware
-
By Oren Eini on Optimizing the cost of clearing a set
-
By Steve on Optimizing the cost of clearing a set
-
By Oren Eini on Optimizing the cost of clearing a set
Syndication
| Main feed | |
| Comments feed |
Comments
Just gave it a try - Voron.Tryout indeed works, but the unit tests end in a segfault or a deadlock - I'll take a look at this if I find some time over the weekend.
e-tobi, Yes, there seems to be something that we missed there.
Now you're talking. Been waiting for this port.
As an aside, have you had a chance to look at Aerospike? Worth a peek at what they're up to...
I'm feeling uncomfortably excited. I've wanted to use RavenDB on personal projects, but I use Linux almost exclusively.
@J Healy: Aerospike says it's an in-memory database that can handle 100TB of data on just a few servers. The biggest server I can get has 256GB of RAM. Just storing the raw data would take 400 of them. Indexing it would take more. They're almost certainly lying about it being an in-memory database. I'd guess they have some good caching algorithms and efficient point queries but are ultimately serving out of durable storage.
Clearly once they get over the memory capacity of a box they go hybrid...
"You can run Aerospike in pure RAM with spinning disks for persistence or as a hybrid memory database with RAM and flash.
Indexes (primary and secondary) are always stored in DRAM for fast access and are never stored on Solid State Drives (SSDs) to ensure low wear.
Unlike other databases that use the linux file system that was built for rotational drives, Aerospike has implemented a log structured file system to access flash – raw blocks on SSDs – directly. Access is optimized for how flash works – with small block reads and large block writes – and parallelized across multiple SSDs for better throughput.
Per namespace storage configuration – each namespace can be configured to store data on DRAM or on SSDs."
Comment preview