“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.
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 @codspeedhq
Also available
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 @codspeedhq'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.
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.