jma24
Context engineering is allowing me to do things I've always wanted to do but don't have the time/energy. I'm writing in C++, assembly, Rust, Go. I'm fucking with boot loaders and all kinds of things.
It's brought me a far greater understanding of how cryptography, GPUs, CUDA, Apple Metal - all topics I have a vague interest in but have no time to work on.
The current raft of LLM models are genius children. It's like that 15 year old at college. But I have 30 years of experience and a genius child is pure power in my hands.
And it's a genius child that never gets tired. For a few hundred bucks a month I can have 3 geniuses working on my ideas through the night. Last night they wrote 20 different research theses on a topic and benchmarked them all. Then combined them into a best of breed algorithm better than anything that has been done before. It's an amazing world we live in.
I don't write this to throw mud at OP - they are entitled to their opinion. Merely to point out the contrast.
But the strength of Oracle remains OLTP and I don't see customers fleeing to MemSQL for this.
Typical columnar compression gives about 11GB per 1bn rows, so 17bn rows should be 187GB. The AWS machines they are using should be c3.4xlarge which are 30GB, and 6 of them is 180GB. But you can't run an in-memory column store at 100% RAM, you need to run it at 50-70% so you have capacity for calculations.
Is it just me or do the results not make any sense? Seems likely they actually had 9.5bn or 4 months data, which conveniently is what the graph shows?