Activity
Stars and mentions · Last 30 days, Oct 7 – Nov 5
Top repositories
lemire’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside lemire’s account where lemire opened or reviewed pull requests in the past 365 days.
Who noticed lemire
Everyone who starred or forked lemire’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories lemire owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Neat result, and good writeup! I don't have time to compare them, but another resource you might look at is Daniel Lemire's "Fast Division": lemire/fast_division If you've come up with something better, I'd encourage you to contact Daniel and see if he's interested in helping you write it up into a paper. He's friendly, and may be better positioned to get the optimizations into mainstream compilers.
Made a chart from Lemire’s published WebSocket results. One client pair: Node + uWebSockets.js leads Bun.serve. Saturated load: Bun.serve leads that stack. My minimum requirement for a “fastest” badge: the workload. lemire/jswebsocket_bench t.co