All of these "fast" databases have a fatal flaw - it takes forever to load the data in the first place. In this case loading takes >1000x longer than the query so loading is all that matters.
All of these "fast" databases have a fatal flaw - it takes forever to load the data in the first place. In this case loading takes >1000x longer than the query so loading is all that matters.
Your complaint only makes sense if you only intend to perform one single query against a dataset.
The response time is quite fantastic (less than a minute), but there are drawbacks: - GC takes in the order of minutes to complete - loading the data takes 90 min from spinning rust
So yeah, it's possible, but your bottleneck becomes the storage driver.
Source: I work at SAP's internal cloud team. For our internal customers running SAP HANA, we offer baremetal machines with up to 6 TiB RAM.
Heavy fixed processing costs up front with the benefit of light variable processing moving forward.
It's far from the correct title. A good part of the optimisation of all modern analysis DBs is in-memory... this is no different and as such he's compared his work against 2 of the major other systems in the space.
I see a lot of critics here... I think the guy should be congratulated for his work - which if you've read through all pages, appears to be done single handed!
There's a lot more to data analysis than loading data off disk.