قد يعجبك
Fantastic talk/quizz by @codspeedhq founders They shared very clear explanations of why pieces of code are fast/slow, and how one can understand why by looking at the final assembly #eurorust25
Time to fix 🔨👷
Today I fixed a problem where our benchmarks were running too slowly for the past two years. Yes, you heard that correctly - the benchmarks run too slow, each run takes over 2 minutes 😠 @overlook_motel and I suspected everything except ... So we use @codspeedhq for continuous…
First @codspeedhq benchmarks in Zig are here! Kudos to @James_Elicx for kickstarting the integration with our instrument hooks!
New feature release today ✨
🚀 Major change in how @codspeedhq analyzes performance tests: Partial Runs are live. Making the performance feedback tighter than ever before. codspeed.io/changelog/2025…
We've just added more minutes of macro runners for open-source repositories! codspeed.io/changelog/2025…
codspeed.io
More Free Macro Runners minutes - Changelog - CodSpeed
All plans now includes 600 monthly macro runner minutes (up from 120) with possible additional minutes for open source projects.
New language support today! (more to come this month, stay tuned 😉)
🚀 Cool news for Go developers! We’re excited to announce that CodSpeed now supports Go 🐹⚡ codspeed.io/changelog/2025…
New blog post on measuring walltime in CI!
We ran over 100 Walltime benchmarks on GitHub-hosted runners and compared them to our Macro Runners, and the variance difference is significant. 2.66% vs. 0.56% and that’s the difference between 45% false positives and 0.04% codspeed.io/blog/benchmark…
New improvements! 🚀
Really excited to get those improvements out for the profiling experience with CodSpeed⚡
We're launching a new product! 🚀 Check it out: p99.chat
Announcing p99.chat, the assistant for software performance optimization 🚀 Describe your performance challenge, share your code, and p99 will analyze, instrument, and visualize the results, cutting the traditional setup overhead down to seconds!
We’re at @pyconit with @adriencaccia We’ll quizz you on Python performance again tomorrow! See you in room lasagna at 11:45!
We’re in #PyConUS ! And this time, with a booth, don’t hesitate to come by!
We just improved our C++ integration. Now with first-class Bazel support for larger projects! codspeed.io/changelog/2025…
We just released support for C++ benchmarks, enabling the use of our google benchmark compatibility layer to measure the performance of C++ codebases!
Super excited about our latest changes to make performance testing more accessible! ✅ The Free plan now includes private repositories (up to 5 users) ✅ Macro Runners are now globally available (bare-metal ARM64, 16 cores, 32GB RAM) with 120 min/month included for free
We now support sharded benchmark execution to provide even faster performance feedback!
Yesterday, we revised the permissions of our GitHub App to allow our Macro Runners to operate on user repositories rather than just organizations 🚀 We added a page in the documentation describing the permissions we use and why we need them. 👇 docs.codspeed.io/integrations/p…
Day 3 of the Advent of CodSpeed is done! You can still be a part of it and test your code's performance against the other participants at codspeed.io/advent
[Sponsored post] This December, @codspeedhq is hosting an epic Rust Performance Leaderboard for the Advent of Code! 🦀 Compete to submit the fastest solutions and win amazing prizes like a MacBook, Nintendo Switch, and more! 🏆🚀 Learn more here ➡️ codspeed.io/advent…
United States الاتجاهات
- 1. Bears 71.7K posts
- 2. Bills 132K posts
- 3. Falcons 45.3K posts
- 4. Snell 17.9K posts
- 5. Josh Allen 22.8K posts
- 6. #Dodgers 12.9K posts
- 7. Jake Moody 8,218 posts
- 8. Caleb 40.3K posts
- 9. Bijan 28.1K posts
- 10. Turang 3,356 posts
- 11. phil 147K posts
- 12. #NLCS 11.4K posts
- 13. Swift 285K posts
- 14. Roki 5,511 posts
- 15. Jayden Daniels 8,595 posts
- 16. AFC East 7,684 posts
- 17. Brewers 43.1K posts
- 18. Joe Brady 4,314 posts
- 19. Commanders 44.5K posts
- 20. McDermott 6,535 posts
Something went wrong.
Something went wrong.