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
As you can see by simply blaming the README.md file, the benchmarks have been executed more than 5 years ago, which is far before the creation of that issue and the introduction of that regression.
Can the benchmark be improved? Of course!
Have we been unfair? Absolutely no.
Sorry I didn't mean to imply any wrongdoing or anything, I didn't notice the benchmarks were that old! I just like accurate benchmarks so I can make good decisions about what packages to use :)
Gobd
changed the title
Benchmark results are unfair to jsonwebtoken
Benchmark results need updating
Jan 12, 2025
See auth0/node-jsonwebtoken#966 and update the benchmarks with the best practices suggested to make benchmark results reflect current versions.
The text was updated successfully, but these errors were encountered: