jma24

5 ms·

1. 1.▲
   by jma24 4mo ago

   Give me a 48 and we'll talk.
2. 2.▲
   by jma24 4mo ago

   Better sell it fast before the M5 ones come out.
3. 3.▲
   by jma24 4mo ago

   It's a really interesting PoV, and one I'm in polar opposition to. 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
4. 4.▲
   by jma24 9y ago

   Fascinating read Dennis - do keep it up.
5. 5.▲
   An Oracle Database In-Memory FAQ(bluefinsolutions.com)

   3 points by jma24 12y ago|0 comments
6. 6.▲
   by jma24 12y ago

   The much bigger problem with Oracle In-Memory is that a lot of operations like joins and sorts often happen in the SGA, in row form. So you end up needing a truckload of SGA for temporary calculations. And when the SGA runs out, which it in
7. 7.▲
   by jma24 12y ago

   Oracle designed their Database In-Memory Option specifically for these sorts of scenarios. But it's a fairly crudely designed column store cache and MemSQL are right to bash them. But the strength of Oracle remains OLTP and I don'
8. 8.▲
   by jma24 12y ago

   Doing some basic math... Wikipedia is around 80m rows a day, so 4 months of Wikipedia is around 9.5bn rows. But they show 17bn on the graph. Typical columnar compression gives about 11GB per 1bn rows, so 17bn rows should be 187GB. The AWS m