noisepage
sled
noisepage | sled | |
---|---|---|
4 | 37 | |
1,677 | 7,772 | |
- | - | |
0.0 | 1.8 | |
over 1 year ago | 21 days ago | |
C++ | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
noisepage
-
The Part of PostgreSQL We Hate the Most (Multi-Version Concurrency Control)
> Carne
Okay, so, noisepage appears to be open source https://github.com/cmu-db/noisepage/
But I can't find the Ottertune Github page
Is any part of Ottertune open source?
-
Rethinking Stream Processing and Streaming Databases
I was one of the main authors of a research project called Peloton (https://github.com/cmu-db/peloton) which was later rebranded to NoisePage (https://github.com/cmu-db/noisepage). The initial version of RisingWave actually borrowed a lot from Peloton (fun fact: that's also how DuckDB https://duckdb.org/ started!), but we decided to rewrite in Rust due to development cost and security (e.g., memory leakage) considerations (more info: https://www.risingwave-labs.com/blog/building-a-cloud-database-from-scratch-why-we-moved-from-cpp-to-rust/).
-
Show HN: OtterTune – Automated Database Tuning Service for RDS MySQL/Postgres
> If I may, can you please shed light on why Peloton had to be archived and in essence re-done with OtterTune. Interested in your team's learnings from it from a software engineering point of view.
Peloton and OtterTune are completely different projects. Peloton was abandoned and rewritten as NoisePage (https://noise.page). OtterTune has always been OtterTune.
See this recent interview where I discuss why we gave up on Peloton:
https://www.ibm.com/cloud/blog/database-deep-dives-with-andy...
> - How did the team ensure this project doesn't suffer from the same disadvantages as its predecessor?
Again, different projects. OtterTune is all about not having to modify the internals of Postgres, MySQL, and any other DBMS. This is why we were able to support Oracle in the academic version in a short amount of time:
https://ottertune.com/blog/vldb-autonomous-database-tuning-i...
> - What would you advise other teams undertaking a rewrite to pay off their tech debts?
It is hard for to provide general advice for this question because every situation is different.
> How does this project compare to / contrast with Google's and SingleStore's efforts in this space?
I am not familiar with Google or SingleStore using ML in the manner that we are with OtterTune to tune configuration knobs. Or at least I have not seen anything public about it.
These days Oracle is the most aggressive with pushing automated tuning capabilities (Oracle's autonomous DBaaS, AutoPilot for MySQL Heatwave). The difference with these approaches and OtterTune is that right now we are focused on configuration tuning (to avoid data privacy issues) and our core approach is platform/DBMS agnostic.
> Any chance we see you do a Peter Bailis and Sisu Data this? (:
I don't know what you mean by this? Peter Bailis is the Ryan Gosling of databases.
-
Resumable Allocator?
The state of the art for this sort of thing is (Leanstore/Umbra - https://umbra-db.com/) or the new NoisePage database (https://github.com/cmu-db/noisepage/tree/master/src/storage). There is also the HyRise database, but that one focuses more on datasets that fit entirely in memory (https://hpi.de/plattner/projects/hyrise.html)
sled
-
SableDb – a key/value store that uses RocksDB and Redis API (written in Rust)
a few times, seems interesting. The author's also built a lot of other cool concurrency primitives for Rust as well.
[0] https://github.com/spacejam/sled
-
Is Something Bugging You?
- Dropbox [3] uses a similar approach but they talk about it a bit more abstractly.
Sans-IO is more documented in Python [4], but str0m [5] and quinn-proto [6] are the best examples in Rust I’m aware of. Note that sans-IO is orthogonal to deterministic test frameworks, but it composes well with them.
With the disclaimer that my opinions are mine and mine alone, and don’t reflect the company I work at —— I do work at a rust shop that has utilized these techniques on some projects.
TigerBeetle is an amazing example and I’ve looked at it before! They are really the best example of this approach outside of FoundationDB I think.
[0]: https://risingwave.com/blog/deterministic-simulation-a-new-e...
[1]: https://risingwave.com/blog/applying-deterministic-simulatio...
[2]: https://dropbox.tech/infrastructure/-testing-our-new-sync-en...
[3]: https://github.com/spacejam/sled
[4]: https://fractalideas.com/blog/sans-io-when-rubber-meets-road...
[5]: https://github.com/algesten/str0m
[6]: https://docs.rs/quinn-proto/0.10.6/quinn_proto/struct.Connec...
-
RFC: redb (embedded key-value store) nearing version 1.0
Sled uses bw-tree actually https://github.com/spacejam/sled/wiki/sled-architectural-outlook
-
Production grade databases in Rust
There is a valid argument to be made for threads over async in a large percentage of use cases where async is considered the default. If this is what you are referring to however, I don't think they ever referred to async as completely useless: https://github.com/spacejam/sled/issues/1123.
-
Best local database that works on all platforms including web?
Have you looked into other pure-Rust databases as well, such as sled or GlueSQL which has an SQL interface on top of sled? I wonder how those would compare to Persy.
-
Are there any embedded databases that have multiple-process support?
I'm not sure what you need. Are these of any use? https://github.com/meilisearch/heed https://github.com/spacejam/sled
- Some key-value storage engines in Rust
-
Are there a demand for management system of embedded storage like RocksDB? I plan to build one in Rust as the language becoming a core of many popular databases but wonder if there’s a demand. Can’t find any similar project even in other languages.
There is also Sled but as I understand it that is being reworked to use the author's new DB core Marble
-
GreptimeDB: a new open source database designed for large-scale time-series data storage and processing, written in rust
There are some databases like sled/FlashDB designed to be embedded to other applications even bare metal microcontrollers. But I do doubt the potential bussiness value of a pure embedded database.
-
Ask HN: Serverless” key value store with transactions?
https://github.com/spacejam/sled
To add transaction support, you probably need a good understanding of how the memtable works in Log Structured Merge trees:
What are some alternatives?
openstack-ansible-os_trove - Role os_trove for OpenStack-Ansible. Mirror of code maintained at opendev.org.
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
bustub - The BusTub Relational Database Management System (Educational)
rust-rocksdb - rust wrapper for rocksdb
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
redis-rs - Redis library for rust
MongoDB - The MongoDB Database
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
ClickHouse - ClickHouse® is a free analytics DBMS for big data
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
heed - A fully typed LMDB wrapper with minimum overhead 🐦
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...