227 karma · joined January 9, 2016
I don't know about others, but sessions that are idle > 1h are definitely not a corner case for me. I use Claude code for personal work and most of the time, I'm making it do a task which could say take ~10 to 15mins. Note that I spend a lot of time back and forth with the model planning this task first before I ask it to execute it. Once the execution starts, I usually step away for a coffee break (or) switch to Codex to work on some other project - follow similar planning and execution with it. There are very high chances that it takes me > 1h to come back to Claude.
Having said that, this definitely does look to be an impressive feat of engineering!
It is a B-Tree where updates to the tree are buffered in the branch nodes and are propagated down to the leaf nodes at a later point in time.
[1] https://mymodernmet.com/ancient-egyptians-attendance-record/
https://www.joelonsoftware.com/2003/10/08/the-absolute-minim...
[1] : https://en.wikipedia.org/wiki/Bloom_filter#Algorithm_descrip...
They claim that none of the Bogus patches were merged to the Stable code line :
>Once any maintainer of the community responds to the email,indicating “looks good”,we immediately point out the introduced bug and request them to not go ahead to apply the patch. At the same time, we point out the correct fixing of the bug and provide our proper patch. In all the three cases, maintainers explicitly acknowledged and confirmed to not move forward with the incorrect patches. This way, we ensure that the incorrect patches will not be adopted or committed into the Git tree of Linux.
I haven't been able to find out what the 3 patches which the reference are, but the discussions on Greg's UMN Revert patch [2] does indicate that some of the fixes have indeed been merged to Stable and are actually Bogus.
[1] : https://www-users.cs.umn.edu/~kjlu/papers/clarifications-hc....
[2] : https://lore.kernel.org/lkml/20210421130105.1226686-1-gregkh...
Aqua looks very similar to Oracle's Smart Scan, which is available on Exadata [1] [2].
[1] https://blogs.oracle.com/infrastructure/what-is-smart-scan
In Oracle 21c and the Autonomous JSON Database, we introduced a new Native JSON Datatype with it's own Binary Storage format called OSON[1]. With OSON, you can perform partial updates on a json document. The added benefit is that this results in significantly lesser redo log size.
Oracle's In-Memory option offers dual Row and Columnar storage for Hybrid Transactional/Analytical workloads. The paper describing the feature was published to VLDB in 2015 : https://dl.acm.org/doi/10.14778/2824032.2824061
>Autonomous JSON database gives you 2x throughput consistently across different workload types and collection sizes.
This is great!
>The result is a no-compromise document database providing low latency CRUD operations and full ACID consistency.
The recent Jepsen report[1] highlights some of the major transaction consistency issues with MongoDB and why it might not be suitable for all workloads.