-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offer and update info picobase64 #9
Comments
Hi @GermanAizek ! I should be able to take a look at this this week and update the benchmarks |
Ok |
I updated the results, but I find that with vs2019, the encoding is slower than before, and the decoding hasn't changed. Are you able to run the benchmark and compare with my results? I'll run in clang over the weekend to see if I observe the same thing. |
@gaspardpetit, Ok |
@gaspardpetit,
|
@gaspardpetit, As you can see, encode leading, but I am sure that on Clang result will deteriorate greatly, since I did not divide code configurations for compilers. I'll check on Clang later. |
@gaspardpetit, |
Hi @GermanAizek - I should be able to run the tests again over the weekend and update the tables with your update |
@gaspardpetit
Hello, I saw that you put my repository in your and would like to announce that I will complete this week and make it more faster under MSVC and Clang.
At the moment, I have a very good performance on my server
b64encode()
function, can you check on your devices?Would like to suggest adding benchmarks for GCC.
I can also provide results on my server 2xE5-2699v3@2.30GHz
Repo here:
https://github.com/GermanAizek/picobase64
The text was updated successfully, but these errors were encountered: