asubiotto

4 ms·

1.
Optimizing a CUDA FSST decompression kernel(polarsignals.com)
3 points by asubiotto 3mo ago|0 comments
2.
Questioning an Interface: From Parquet to Vortex(polarsignals.com)
10 points by asubiotto 10mo ago|0 comments
3.
by asubiotto 1y ago
Seems like it. Changed it back!
4.
Das Problem mit German Strings(polarsignals.com)
79 points by asubiotto 1y ago|23 comments
5.
by asubiotto 6y ago
We haven't implemented disk spilling for aggregations yet. It's different from the algorithms discussed in this article in that the amount of memory used is proportional to the number of aggregation groups (buckets), rather than t
6.
Disk Spilling in a Vectorized Execution Engine(cockroachlabs.com)
48 points by asubiotto 6y ago|2 comments
7.
by asubiotto 7y ago
It's hard to say whether one would generally be a bigger gain than another without experimenting. We chose to focus on just execution because it was a relatively smaller project (with less side-effects) that still promised a large perf
8.
by asubiotto 7y ago
CockroachDB does target OLTP workloads. Note that the vectorized SQL engine covered in this blog post is execution-only (and used only for queries that operate on many rows). The storage layer remains row-oriented so the write performance i
9.
by asubiotto 7y ago
+1 avo is on our radar as a tool to use in the future
10.
How We Built a Vectorized SQL Engine in CockroachDB(cockroachlabs.com)
35 points by asubiotto 7y ago|0 comments
11.
by asubiotto 8y ago
Indeed! We spent some time running isolated benchmarks before deciding to dive into the project: https://github.com/jordanlewis/exectoy