News for hackers. Stuff that matters.
Re:MemSQL Does Oracle’s Own Demo Ten Times as Fast, Sixty Ti... by nikita on Wednesday October 01, 2014 @09:17PM (#8398919)
It's hard to define what a "fair" columnar store scan is. We use a technique that is called "segment elimination", which allows to skip over compressed segments of data as you scan. However every solid columnar database uses such techniques. It just happens that Oracle 12c doesn't have the ability to sort columnar indexes, and neither does it have the ability to store columnar indexes on flash or disk, which bloats the overall cost.
Re:MemSQL Does Oracle’s Own Demo Ten Times as Fast, Sixty Ti... by jma24 on Thursday October 02, 2014 @11:55PM (#8404251)
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 invariably does, you end up using TEMPDB. And everything comes to a crawl.
Re:MemSQL Does Oracle’s Own Demo Ten Times as Fast, Sixty Ti... by mbesto on Wednesday October 01, 2014 @09:41PM (#8399018)
How does your tech differ from SAP HANA's columnar DB?