zanmato

3 ms·

1. 1.▲
   by zanmato 5y ago

   For example analytical queries tend to have a big portion of joins and aggregations, they will be more CPU-intensive rather than disk-bound, esp. when complicated data types are involved such as decimal. Further more, traditional databases
2. 2.▲
   by zanmato 5y ago

   It’ll require software strategies such as splitting the working set into multiple pieces and dealing with them one by one. In some extreme cases, for example consider a huge hash table used in a hash join that exceeds the max GPU memory, mo
3. 3.▲
   by zanmato 5y ago

   Yeah this is THE major point of this work ;)
4. 4.▲
   by zanmato 5y ago

   Basically this article does the similar thing with BlazingSQL. Actually both are built on top of the cuDF project. The difference is that TiDB is an HTAP database and this article describes how we empower TiDB’s analytical processing by lev