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
Since glibc continues improving its performance a years-long, the latest version of glibc (2.35) delivered from ubuntu 22.04 seems having a better performance than the strings::memcpy_inlined function, which is currently using in Starrocks writen by Google in 2012.
I have done a bunch of tests with different compiler's parameters, as specially with SIMD instructions. Here is the results:
with no SIMD parameters. It means that the strings::memcpy_inlined function falls back to glibc memcpy, the performance is therefore equivalent to each other.
@stdpain Would you mind to share or opensource your benchmark code in Starrocks? So, I could run it on our latest commercial servers, such as intel Gold 6130, Intel Platinum 8338C and Amd Genova, and give you feedback of what I will get
@stdpain Would you mind to share or opensource your benchmark code in Starrocks? So, I could run it on our latest commercial servers, such as intel Gold 6130, Intel Platinum 8338C and Amd Genova, and give you feedback of what I will get
Since glibc continues improving its performance a years-long, the latest version of glibc (2.35) delivered from ubuntu 22.04 seems having a better performance than the strings::memcpy_inlined function, which is currently using in Starrocks writen by Google in 2012.
I have done a bunch of tests with different compiler's parameters, as specially with SIMD instructions. Here is the results:
with -mavx2 only, reduce 43% time in average
with -mavx2 and -mavx512f
with no SIMD parameters. It means that the strings::memcpy_inlined function falls back to glibc memcpy, the performance is therefore equivalent to each other.
The tests are based on
Intel Xeon Silver 4214 46Core, 256GB Mem
Ubuntu 22.04, gcc 11.4.0, glibc 2.35
test code snippets
CPU Flags
The text was updated successfully, but these errors were encountered: