We handle performance, so you can focus on shipping.
New York, NY
Joined October 2022
- Tweets201
- Following2
- Followers529
- Likes135
CodSpeed retweeted
JUST IN: Rust Foundation Welcomes New Members: CodSpeed, Haevek, Perplexity, and Software Stewardship Lab
ALT Image: JUST IN: Rust Foundation Welcomes New Members: CodSpeed, Haevek, Perplexity, and Software Stewardship Lab
CodSpeed retweeted
Proud to announce that @CodSpeed has joined the Rust Foundation as a Silver member!
We’re all-in on making Rust (and everything around it) fast and staying that way. Supporting the Project that makes that possible felt like the obvious next step.
CodSpeed retweeted
Significant `jiter` release, in particular this includes SIMD support for x86, which should give up to 7x performance improvement for parsing long strings.
There are also significant improvements for tape reuse, arm64 string SIMD, float parsing and more.
jiter is the most used 3rd party JSON library in Python as a dependency of @pydantic validation.
it's also used in Pydantic Monty, and in Pydantic Logfire via datafusion-functions-json.
Short story: apply strict constraints, provide clear benchmarks for the thing you want to improve, use @codspeed, let fable and astra do their thing.
github.com/pydantic/jiter/re…
CodSpeed v5 is out, now with more accurate cycle estimation and the ability to exclude allocators from the simulated execution ⚡
CodSpeed v5 is out, with two big changes to how we measure your code.
First, cycle estimation. Until now, every instruction was charged the same cost, but a `div` is ~25x more expensive than a `mov` on real hardware. We patched Callgrind to emit per-instruction metadata and built a cost model on top, weighting every instruction by its measured cost on real CPUs, cache misses included. Replacing a division with a multiply now shows up in your benchmarks the way it shows up in production. Just upgrade and you'll have it on by default.
Second, allocation exclusion. Allocators are non-deterministic by design: their cost depends on the OS, the implementation, the version. If you're optimizing your own code, that's pure noise. v5 tags every allocator frame in the call graph and subtracts its time from the reported value. The flamegraph still shows the frames, only the number changes. Opt in with the `exclude-allocations` flag.
Just upgrade your action to CodSpeedHQ/action@v5 and you're set.
Only your code, at its real cost 🚀
ALT CodSpeed v5: Only your code, at its real cost
🥇 @codspeed: the performance platform that catches regressions before they hit production, autonomously suggesting and validating optimizations across CPU modeling, profiling, heap analysis, and more. Free for open source.
Thank you for supporting #rustconf at the Gold Level, CodSpeed! codspeed.io
CodSpeed retweeted
tfw you spend a few hours optimizing and you finally see the @codspeed GH action report
hello @1Password, we should talk
“op read” (@1Password cli) takes almost 1s to read a secret. Apple’s “security” is sub 100ms. Is there some trick to make 1Password faster (on an M4 Max machine?!) so I can actually use it in scripts?
To be honest Apple’s 90ms for a secret retrieval is questionable too.
New flamegraph feature ✨
A flame graph that merges all threads is lying to you. That "hot" function might be a GC thread, not the request path.
You can now filter flame graphs down to specific processes and threads, or split them to see exactly how the work is distributed in @codspeed
Also available in the CodSpeed MCP: your coding agent profiles the exact worker it's optimizing.
CodSpeed retweeted
Your benchmark moved. You didn't touch the code.
A compiler bump, a new system lib, a different CPU flag. Any of it shifts the numbers.
CodSpeed now diffs the environment between two runs, so you know when it's the toolchain that changed and not your code.
codspeed.io/changelog/2026-0…
This is exactly what we had in mind building our MCP server. Your agent gets the same level of details you can get by browsing profiling data and finally have insights on what and how to optimize
Performance work with @codspeed's MCP server feels like a cheat.
Instead of stumbling round in the dark with a machete, attempting to hack at random patches of code, Fable and I are a sniper - the MCP tells me which code is slow, we figure out how to make it fast. Rinse. Repeat.
CodSpeed can now optimize your code for you!
The agent runs benchmarks with CPU simulation, generates profiling data, and iterates: edit, measure, compare. It stops when it finds something measurable.
You get the diff + a PR.
2/ @codspeed (a software performance platform) uses Claude Managed Agents w/ @blaxelAI self-hosted sandboxes.
customer code remains within their security boundary w/in the @blaxelAI sandbox.
blaxel.ai/blog/codspeed-uses…
CodSpeed retweeted
.@codspeed uses Claude Managed Agents + @blaxelAI sandboxes to build an AI agent that:
-> ingests customer code
-> benchmarks it
-> iterates on changes
-> finds performance improvements
nitter.cf/ClaudeDevs/status/2065…
Claude Managed Agents can operate in a sandbox you control, on your own infrastructure or with any provider you choose.
Today we added new guides for @blaxelAI, @e2b, @googlecloud, @namespacelabs, and @superserve_ai, so you can choose the best fit for your use case.
CodSpeed retweeted
"I use it every day and honestly can't live without it. Saves me tons of time."
@hardfist_1, lead of @rspack_dev at ByteDance, on the CodSpeed Wizard.
So proud and excited to build the performance agent for the fastest projects on the planet!
