You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Improve Nullable support during dataframe arithmetic operations #6825
During arithmetic operations dataframe performs cloning the left side column into the result to have validity bitmap and than checks the right side validity bitmap for NULL value.
For example for Multiply we do cloning in case of inPlace parameter is set to false (default behavior):
and inside container for each value we check validity:
for (int i = 0; i < span.Length; i++)
{
if (BitmapHelper.IsValid(right.NullBitMapBuffers[b].ReadOnlySpan, i))
{
span[i] = (double)(span[i] * otherSpan[i]);
}
else
{
left[index] = null;
}
index++;
}
Validity check is a very slow operation. It's possible to calculate Raw values and then use binary logic (AND) for calculating validity bitmap for whole byte.
//calculate raw values
for (int i = 0; i < span.Length; i++)
{
resultSpan[i] = (double)(span[i] * otherSpan[i]);
}
//Calculate validity (nulls)
resultValidityBitmap = Bitmap.ElementWiseAnd(validityBitmap, otherValidityBitmap));
changed the title [-]Improve Nullable support during dataframe arithmetic operations and avoid excessive cloning of the left side[/-][+]Improve Nullable support during dataframe arithmetic operations [/+]on Sep 21, 2023
It's also possible to get rid of cloning of the left side and create new empty column for results instead. However investigation shows, that there isn't any dramatical improvement of performance on avoiding Cloning. On the other hands, it requires quite a lot of code changes in both PrimitiveDataFrameColumn.BinaryOperations.tt and PrimitiveDataFrameColumn.BinaryOperationImplementations.Exploded.tt (current implementation of DataFrame provides two different implementations for arithmetic calculation: one for PrimitiveDataFrameColumn and another for inheritors, like Int32DataFrameColumn and etc). So I decided to postpone remediation of the left part cloning until templates files are simplified and duplicating implementations are removed.
Here is the result of my experimentation (first column is speed with just enhanced nullable, second column is enhanced nullable + avoiding cloning):
Activity
[-]Improve Nullable support during dataframe arithmetic operations and avoid excessive cloning of the left side[/-][+]Improve Nullable support during dataframe arithmetic operations [/+]asmirnov82 commentedon Sep 21, 2023
It's also possible to get rid of cloning of the left side and create new empty column for results instead. However investigation shows, that there isn't any dramatical improvement of performance on avoiding Cloning. On the other hands, it requires quite a lot of code changes in both PrimitiveDataFrameColumn.BinaryOperations.tt and PrimitiveDataFrameColumn.BinaryOperationImplementations.Exploded.tt (current implementation of DataFrame provides two different implementations for arithmetic calculation: one for PrimitiveDataFrameColumn and another for inheritors, like Int32DataFrameColumn and etc). So I decided to postpone remediation of the left part cloning until templates files are simplified and duplicating implementations are removed.
Here is the result of my experimentation (first column is speed with just enhanced nullable, second column is enhanced nullable + avoiding cloning):

asmirnov82 commentedon Sep 29, 2023
Final results, when PR is implemented