art049
Joined 4 years ago
Karma
97
Submissions
33
Member since
Mar 2
Recent submissions
Comment · 8 months ago
Comment · 1 year ago
Yes definitely, this is what we already do with cpu simulation. But we had many people with benchmarks using syscalls for network,fs and other resources. And we found the only solution for this is to actually measure wall time
Comment · 1 year ago
I hadn't considered this, but it would be really interesting to take it into account. Given that the size of the benchmark suites directly affects the false positive rate, and counterintuitively, the more benchmarks in the suite, the more the chances of false positives, even with super steady benchmarks. (Thanks, it could also be an interesting follow-up article!)
We’re building the continuous performance optimization platform. We help engineering teams catch performance regressions before they ship, with sub-1% measurement variance. We’re already trusted by teams at Cloudflare, Vercel, Mozilla, Pydantic, and Astral (Ruff, uv).
We’re a small, deeply technical team looking for engineers who want real ownership and the chance to ship end-to-end. Competitive salary, stock options, generous PTO.
Senior Systems Engineer: CPU simulation tooling, language runtime internals (CPython, V8), kernel I/O emulation. C/C++/Rust/Zig.
Senior Full-stack Engineer: React/Next.js, Node.js/TypeScript/GraphQL, GitHub/GitLab integrations, Rust data pipelines.
Senior/Lead AI Engineer: Agent layer, eval methodology, context pipelines, model selection. Python/FastAPI.
Graphic/UI Designer: Visual identity and product experience for a developer tool.
More details at https://careers.codspeed.io. Apply at [email protected]