Tokio vs async-std: source lines of code compared

The Tokio vs async-std comparison on OctoCounts shows side-by-side source line counts for tokio-rs/tokio and async-rs/async-std, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of tokio-rs/tokio and async-rs/async-std using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-14, tokio-rs/tokio contains 89,131 total lines (63,411 code) across 542 files, while async-rs/async-std contains 18,552 total lines (14,817 code) across 267 files as of 2026-10-31. tokio-rs/tokio has about 4.3x the counted code lines of async-rs/async-std under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metrictokio-rs/tokioasync-rs/async-std
Files542267
Total lines89,13118,552
Code lines63,41114,817
Comment lines10,7931,143
Blank lines14,9272,592
Languages counted44

Top languages in tokio-rs/tokio: Rust (98.8% of code), TOML (1.1% of code), JSON (0.1% of code). Top languages in async-rs/async-std: Rust (99.2% of code), TOML (0.7% of code), Shell (0.1% of code). Rust, TOML, Markdown appear in both top language lists; JSON appears only in tokio-rs/tokio's top languages; Shell appears only in async-rs/async-std's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/tokio was counted at ref master (commit f3e855fa55d6) on 2026-11-14; async-rs/async-std was counted at ref main (commit 844b55253152) on 2026-10-31. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. tokio-rs/tokio: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. async-rs/async-std: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: tokio-rs/tokio is the Tokio workspace — the asynchronous runtime crates, their utilities, and the surrounding test and CI infrastructure, in Rust. async-rs/async-std is the async-std repository — a Rust library exposing asynchronous versions of the standard library's API, with its own tests and documentation. Both repositories are Rust async-runtime source trees, counted on the dates shown above.

Both counted trees are predominantly Rust, as each per-language table shows, so the totals measure two codebases of the same kind — asynchronous runtimes for the same language and ecosystem.

Tokio's repository is organized as a workspace of multiple published crates, while async-std's is organized around a single library surface modeled on the standard library — a structural difference the file layout of each repository makes visible.

Neither number speaks to runtime throughput or latency for a specific workload: async runtime performance depends on scheduler configuration, I/O patterns, and the application built on top, not on repository line counts.

Sources: tokio-rs/tokio repository (workspace of runtime crates) · async-rs/async-std repository. Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, tokio-rs/tokio or async-rs/async-std?

As of 2026-11-14, tokio-rs/tokio contains 89,131 total lines (63,411 code) across 542 files, while async-rs/async-std contains 18,552 total lines (14,817 code) across 267 files as of 2026-10-31. tokio-rs/tokio has about 4.3x the counted code lines of async-rs/async-std under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for tokio-rs/tokio, async-rs/async-std, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. tokio-rs/tokio was counted at ref master (commit f3e855fa55d6) on 2026-11-14; async-rs/async-std was counted at ref main (commit 844b55253152) on 2026-10-31. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.