Skip to content

Conversation

@rouault
Copy link
Member

@rouault rouault commented Nov 16, 2025

timings wih a SSE2 optimized build:

  • before:
    testByte(): 0.306
    testInt8(): 5.779
    testUInt16(): 0.726
    testInt16(): 2.519
    testUInt32(): 6.933
    testInt32(): 7.537
    testUInt64(): 8.140
    testInt64(): 7.807
    testFloat16(): 12.953
    testFloat32(): 6.105
    testFloat64(): 6.525

  • after
    testByte(): 0.308
    testInt8(): 0.440
    testUInt16(): 0.710
    testInt16(): 0.897
    testUInt32(): 1.986
    testInt32(): 1.826
    testUInt64(): 6.004
    testInt64(): 5.641
    testFloat16(): 2.120
    testFloat32(): 1.811
    testFloat64(): 3.571

@rouault rouault added this to the 3.13.0 milestone Nov 16, 2025
…n-complex types (but Byte and UInt16 that were already optimized)

timings wih a SSE2 optimized build:

- before:
testByte(): 0.306
testInt8(): 5.779
testUInt16(): 0.726
testInt16(): 2.519
testUInt32(): 6.933
testInt32(): 7.537
testUInt64(): 8.140
testInt64(): 7.807
testFloat16(): 12.953
testFloat32(): 6.105
testFloat64(): 6.525

- after
testByte(): 0.308
testInt8(): 0.440
testUInt16(): 0.710
testInt16(): 0.897
testUInt32(): 1.986
testInt32(): 1.826
testUInt64(): 6.004
testInt64(): 5.641
testFloat16(): 2.120
testFloat32(): 1.811
testFloat64(): 3.571
@msmitherdc
Copy link
Contributor

are the timings swapped? The before are less than the after.

@rouault
Copy link
Member Author

rouault commented Nov 16, 2025

are the timings swapped?

did you look at the corrected version in github UI (the original one at submission time of the PR was indeed swap)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants