3 ms·
> but it seems like you could store data columnulary by type to get efficient vectorization and access patterns for operations over types I tried at first to
by mamcx 3y ago
> but it seems like you could store data columnulary by type to get efficient vectorization and access patterns for operations over types
I tried at first to be fully columnar, then cave and try hybrid then now I doing mostly rows with 2d NDArrays.
The major reason is that going columnar flip everything and then I need to recreate tons of API, in special costly with FFI or APIs. I was looking into mimicking kdb+, and yes, that is what they end up doing. This lead to a more insular community (that I don't have but well, that is a worry!)
- foota 3y agoAh yeah, that makes sense. Even having types stored in arrays though could be better than the typical graph like structure you might get from an OO language.