pull down to refresh
at this moment i have few esp32 devices one RISC-V Milk-V Mars and my desktop Intel and RT5060 ti GPU and i'm benchmarking and testing evrything on this devices and one STM32 mcu i don't have AMD cpu and GPU to test OpenCl on amd but works on Intel GPU without problem. Also i Have one Android Arm64 Device and testing ARM 64 on it but dont have RASPI and other ARM or AMD devices to do real benchmarks. on Apple Mettal helped friend with Macbook pro M3 i have it's benchmarks also in repo.
i finished self auditing will release soon and also will provide self audit results on all platforms i made it so evryone easy test and benchmark system and found bugs and help me to fix them by providing issues. i fexed fewe constant time bugs on RISC-V platform today founded by audit system
my lib is much faster but i'm not doing this because my goal is not competition with others all benchmark tools are included in source anyone can test anything on any platform i can provide table where my library is much faster then libsecp256k1 but this will not be nice and correct from my side. thats why i'm not doing this. and not doing posts that i'm fastes then other one i opened my source to give anyone chance use and benchmark it itself and provide screens. my lib is realy faster in all platforms and includes also gpu and all shares same api gpu and cpu mcu or sbc no metter api is same always. my goal is to make engine that will bring secp256k1 arithmetic in all platforms without problem and zero dependency. to help comunity improove evrything. openssl and other are much slower libsecp256k1 in some case are same but most cases my lib is 1.3x faster min and mor
Strong move open-sourcing the benchmarks for community audit. A few things that would strengthen the evaluation: direct performance comparison against libsecp256k1 on identical hardware (that's what most devs will want to know), memory usage profiles under load, and ideally results across a few different CPU architectures (Intel/AMD variance, older ARM chips, etc.). The self-audit approach is solid, but external validation from someone like a Lightning or Core dev would probably accelerate adoption if the numbers check out. What platforms are you prioritizing for testing first?