Le 03/10/2023 à 01:36, Matt Topol a écrit :
The cost of conversion is actually significantly higher than the actual
overhead of simply accessing the values in either representation, leading
to a high potential for bottleneck. For systems like Velox and DuckDB where
it's important to be able to return results as fast as possible, if they
have an operation with a throughput of several hundred MB/s or even G/s,
this conversion cost would become a huge bottleneck to returning results
given several cases of converting Raw Pointer views to the offset-based
views go as low as ~22MB/s.
I think you misread the benchmark numbers. It's 22 MItems/s, not 22 MB/s.
Since that number is for the kLongAndSeldomInlineable case, I assume the
MB/s would two or three orders of magnitude higher.
Regards
Antoine.
