The conversation

Building & toolsEditorial digest

Skip the optimization that is not your bottleneck

popzxc explains a storage design using ordinary serialization after trying a more complex zero-copy approach. File-system costs were not dominant. Data is written after indexing, writes take a lock, and query transactions hold loaded data only for their lifetime.

Original excerpt

“Well, it's hard to give a concise overview, but in short -- I use `wincode` for serde (without zero-copy deserialization though; I've tried zero-copy”

Read the full original
Original discussionHacker News discussion
Discuss

What was this responding to?

Parent context · original excerpt

HA

Can you tell about how you write/read your data to/from disk? I‘m also exploring the incremental world using an approach like salsa+rocksdb. Similar like https://docs.rs/qbice/latest/qbice/ . Would be great to learn about your approach.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 0

Direct replies available in this import. Original-language excerpts.

This sample contains no direct replies. Follow the source to read the full discussion.

Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.