Unified testing shows that Campfire's Rust version has approximately twice the throughput of the Go version; the early claim of 150 times has been questioned

Article

DHH The claim that the Rust version's 150 performance was twice as high has come under heavy scrutiny. Is readability still worth pursuing after code is written?

Beating AI news: the renowned Rails web framework's creator AI had DHH port his company's AI chat software Campfire to 37signals, Go, and Elixir. In the initial tests, the Rust version handled approximately Rust chat-page requests per second, while the original Ruby version handled only approximately 36000. 240 DHH formerly favored Ruby, primarily valuing its development efficiency and code readability. He is now reconsidering whether, if AI is responsible for writing code and humans no longer read it line by line, there is still any need to sacrifice execution speed for development convenience.

Vercel CEO Guillermo Rauch strongly supported this judgment. Vercel once spent 15 months porting approximately 70000 lines of Go code in the Turborepo build tool to Rust. Although the team believed that Rust was better suited to low-level system operations, the cost of manual migration was too high, and the return on investment once sparked internal controversy. Rauch believes that AI has reduced the cost of writing code, so languages that were previously convenient for human development may no longer be the most cost-effective choice for businesses.

However, the performance figures for DHH were quickly questioned. After examining the code repository, Elixir creator José Valim found that the Rust version had undergone hundreds of commits and multiple rounds of performance optimization, whereas the Elixir version had essentially remained in its initial ported state. The architectures also differed. Elixir concentrated database operations in a single process, while Rust used optimizations such as concurrent reads and caching. Such a test makes it difficult to establish how much of the performance gap actually comes from the languages themselves.DHH responded that he had asked the top-tier AI Agent to bring out the best performance possible from each language. If the Agent cannot find ways to optimize Elixir, that is also something developers must face in real-world development.

The community then continued optimizing the different versions.October 8 The updated unified test showed that the Rust version handled approximately 106000 chat-page requests per second, the Go version approximately 53000 requests, and the Rust version was still approximately twice as fast.

Original link https://m.theblockbeats.info/flash/370782

Key points

DHH had AI port 37signals's chat software Campfire to Rust, Go, and Elixir.
In the early tests, the Rust version handled approximately 36000 chat-page requests per second, while the original Ruby version handled approximately 240.
Unified testing showed that the Rust version handled approximately 106000 requests per second, while the Go version handled approximately 53000.
José Valim pointed out that the Rust version had undergone hundreds of commits and multiple rounds of optimization, whereas the Elixir version had essentially remained in its initial ported state.
DHH stated that he had asked the top-tier AI Agent to bring out the best performance possible from each language.

AI-assisted interpretation

The following is analysis, separate from reported facts. Verify important claims independently.

This news discusses whether AI after participating in code writing, businesses should still prioritize languages that are readable and convenient for development.Rust The version was faster in the tests reported, but the optimization levels and architectures of the different versions were not the same, so the speed gap cannot be simply attributed to the languages themselves.

Why it matters to readers

It reflects that AI after reducing the cost of writing code, the trade-offs among runtime performance, development efficiency, and code readability may once again receive greater attention.

The key point is not that Rust is necessarily faster, but that performance tests must ensure comparable levels of code optimization, architecture, and testing conditions.

Risks and unknowns

The hardware environment, code versions, and complete methodology of the original test were not specified in the evidence.
The optimization levels and architectures of the different implementations varied, so the specific source of the performance gap cannot be confirmed.
The evidence does not specify whether these test results represent performance in production environments.

Unified testing shows that Campfire's Rust version has approximately twice the throughput of the Go version; the early claim of 150 times has been questioned

Article

AI-assisted interpretation

Why it matters to readers

Risks and unknowns

Related Developments

Related concepts

Keep following

Security Center