Skip to content

turbo-persistence: SST write path I/O and allocation optimizations#90542

Open
lukesandberg wants to merge 1 commit intocanaryfrom
sst_writer_buffers
Open

turbo-persistence: SST write path I/O and allocation optimizations#90542
lukesandberg wants to merge 1 commit intocanaryfrom
sst_writer_buffers

Conversation

@lukesandberg
Copy link
Contributor

@lukesandberg lukesandberg commented Feb 25, 2026

What?

Targeted optimizations to the turbo-persistence SST write path, informed by profiling the compaction benchmark with samply.

Changes

  1. sync_allsync_data + parallel syncs (db.rs)

    • Use sync_data() instead of sync_all() for all file syncs in commit() — avoids syncing metadata (timestamps) we don't need for crash safety
    • Parallelize SST and blob file syncs using try_parallel_for_each since they're independent I/O operations
  2. Larger BufWriter capacity (static_sorted_file_builder.rs, meta_file_builder.rs)

    • Increase from default 8 KiB to 256 KiB, batching ~16-64 compressed blocks per write syscall instead of flushing on nearly every block
  3. Software position tracking (static_sorted_file_builder.rs)

    • Replace file.stream_position() with a computed value from block offsets
    • BufWriter does not override Seek::stream_position, so calling it flushes the entire write buffer then issues an lseek syscall — defeating the larger buffer from change Exposing css as next/css #2
  4. Dict-less LZ4 compression uses compress_to_vec (compression.rs)

    • For blocks without a dictionary (value blocks, small value blocks, blobs), use lz4::compress_to_vec which uses a thread-local ExtState with fast reset — no allocation
    • Keep Compressor::with_dict only for dictionary-compressed key blocks where it's actually needed
  5. Better KeyBlockBuilder reservation (static_sorted_file_builder.rs)

    • Pass current_block_size as a size hint to KeyBlockBuilder::new so the initial Vec::reserve is accurate, reducing reallocation during block building

Benchmark Results

Compared canary vs this branch using cargo bench -p turbo-persistence:

Benchmark canary (ms) branch (ms) Change
write/key_8/value_4/entries_853Ki 155.60 146.35 -5.9%
write/key_4/value_32Ki/entries_31 16.08 15.63 -2.8%
write/key_4/value_32Ki/entries_319 20.71 19.16 -7.5%
write/key_4/value_32Ki/entries_3.12Ki 83.56 84.67 ~0% (noise)
compaction/4Mi/commits_8 2.32 2.50 ~0% (noise)
compaction/4Mi/commits_32 605.97 576.79 -4.8%

Note: The benchmarks run single-threaded, so the parallel sync_data optimization (addressing 19% of profiled time) has no visibility here. Real-world impact should be larger, particularly for commits with multiple SST files where fsyncs can be pipelined by the OS.

@nextjs-bot nextjs-bot added created-by: Turbopack team PRs by the Turbopack team. Turbopack Related to Turbopack with Next.js. labels Feb 25, 2026
Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@lukesandberg lukesandberg changed the title improve our basic file io turbo-persistence: SST write path I/O and allocation optimizations Feb 25, 2026
@codspeed-hq
Copy link

codspeed-hq bot commented Feb 25, 2026

Merging this PR will not alter performance

✅ 17 untouched benchmarks
⏩ 3 skipped benchmarks1


Comparing sst_writer_buffers (77e936b) with canary (5f6aa1c)

Open in CodSpeed

Footnotes

  1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@nextjs-bot
Copy link
Collaborator

nextjs-bot commented Feb 25, 2026

Tests Passed

Comment on lines +545 to +553
self.parallel_scheduler
.try_parallel_for_each(&new_sst_files, |(_, file)| {
file.sync_data()?;
anyhow::Ok(())
})?;
self.parallel_scheduler
.try_parallel_for_each(&new_blob_files, |(_, file)| {
file.sync_data()?;
anyhow::Ok(())
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we just concat the iterators and do one parallel for each

@nextjs-bot
Copy link
Collaborator

Stats from current PR

✅ No significant changes detected

📊 All Metrics
📖 Metrics Glossary

Dev Server Metrics:

  • Listen = TCP port starts accepting connections
  • First Request = HTTP server returns successful response
  • Cold = Fresh build (no cache)
  • Warm = With cached build artifacts

Build Metrics:

  • Fresh = Clean build (no .next directory)
  • Cached = With existing .next directory

Change Thresholds:

  • Time: Changes < 50ms AND < 10%, OR < 2% are insignificant
  • Size: Changes < 1KB AND < 1% are insignificant
  • All other changes are flagged to catch regressions

⚡ Dev Server

Metric Canary PR Change Trend
Cold (Listen) 560ms 559ms ▁▁▁█▁
Cold (Ready in log) 557ms 556ms ▂▁▁█▂
Cold (First Request) 1.258s 1.257s ▄▁▁█▄
Warm (Listen) 559ms 559ms ▁▁▁█▁
Warm (Ready in log) 557ms 552ms ▁▁▁█▁
Warm (First Request) 466ms 455ms ▁▁▁█▂
📦 Dev Server (Webpack) (Legacy)

📦 Dev Server (Webpack)

Metric Canary PR Change Trend
Cold (Listen) 456ms 455ms ▅▅▁▅▁
Cold (Ready in log) 436ms 436ms ▁▂█▆▅
Cold (First Request) 1.915s 1.897s ▁▂▆█▄
Warm (Listen) 456ms 456ms ▃▃▃▃▁
Warm (Ready in log) 436ms 437ms ▂▁▇▇▅
Warm (First Request) 1.929s 1.941s ▂▁▄█▃

⚡ Production Builds

Metric Canary PR Change Trend
Fresh Build 5.467s 5.366s ▁▁▁█▁
Cached Build 5.408s 5.331s ▁▁▁█▁
📦 Production Builds (Webpack) (Legacy)

📦 Production Builds (Webpack)

Metric Canary PR Change Trend
Fresh Build 13.971s 14.013s ▁▁▂█▂
Cached Build 14.157s 14.179s ▁▂▃█▂
node_modules Size 475 MB 475 MB ▁▁▁▁▁
📦 Bundle Sizes

Bundle Sizes

⚡ Turbopack

Client

Main Bundles: **399 kB** → **399 kB** ✅ -21 B

80 files with content-based hashes (individual files not comparable between builds)

Server

Middleware
Canary PR Change
middleware-b..fest.js gzip 766 B 761 B
Total 766 B 761 B ✅ -5 B
Build Details
Build Manifests
Canary PR Change
_buildManifest.js gzip 448 B 451 B
Total 448 B 451 B ⚠️ +3 B

📦 Webpack

Client

Main Bundles
Canary PR Change
5528-HASH.js gzip 5.54 kB N/A -
6280-HASH.js gzip 58.3 kB N/A -
6335.HASH.js gzip 169 B N/A -
912-HASH.js gzip 4.59 kB N/A -
e8aec2e4-HASH.js gzip 62.6 kB N/A -
framework-HASH.js gzip 59.7 kB 59.7 kB
main-app-HASH.js gzip 254 B 254 B
main-HASH.js gzip 39.1 kB 39.1 kB
webpack-HASH.js gzip 1.68 kB 1.68 kB
262-HASH.js gzip N/A 4.59 kB -
2889.HASH.js gzip N/A 169 B -
5602-HASH.js gzip N/A 5.55 kB -
6948ada0-HASH.js gzip N/A 62.6 kB -
9544-HASH.js gzip N/A 59 kB -
Total 232 kB 233 kB ⚠️ +721 B
Polyfills
Canary PR Change
polyfills-HASH.js gzip 39.4 kB 39.4 kB
Total 39.4 kB 39.4 kB
Pages
Canary PR Change
_app-HASH.js gzip 194 B 194 B
_error-HASH.js gzip 183 B 180 B 🟢 3 B (-2%)
css-HASH.js gzip 331 B 330 B
dynamic-HASH.js gzip 1.81 kB 1.81 kB
edge-ssr-HASH.js gzip 256 B 256 B
head-HASH.js gzip 351 B 352 B
hooks-HASH.js gzip 384 B 383 B
image-HASH.js gzip 580 B 581 B
index-HASH.js gzip 260 B 260 B
link-HASH.js gzip 2.5 kB 2.5 kB
routerDirect..HASH.js gzip 320 B 319 B
script-HASH.js gzip 386 B 386 B
withRouter-HASH.js gzip 315 B 315 B
1afbb74e6ecf..834.css gzip 106 B 106 B
Total 7.97 kB 7.97 kB ✅ -2 B

Server

Edge SSR
Canary PR Change
edge-ssr.js gzip 125 kB 125 kB
page.js gzip 254 kB 254 kB
Total 379 kB 379 kB ⚠️ +307 B
Middleware
Canary PR Change
middleware-b..fest.js gzip 617 B 612 B
middleware-r..fest.js gzip 156 B 155 B
middleware.js gzip 43.6 kB 43.6 kB
edge-runtime..pack.js gzip 842 B 842 B
Total 45.2 kB 45.2 kB ⚠️ +61 B
Build Details
Build Manifests
Canary PR Change
_buildManifest.js gzip 715 B 718 B
Total 715 B 718 B ⚠️ +3 B
Build Cache
Canary PR Change
0.pack gzip 4.02 MB 4.03 MB 🔴 +7.88 kB (+0%)
index.pack gzip 104 kB 104 kB
index.pack.old gzip 103 kB 104 kB
Total 4.22 MB 4.23 MB ⚠️ +8.6 kB

🔄 Shared (bundler-independent)

Runtimes
Canary PR Change
app-page-exp...dev.js gzip 318 kB 318 kB
app-page-exp..prod.js gzip 169 kB 169 kB
app-page-tur...dev.js gzip 318 kB 318 kB
app-page-tur..prod.js gzip 168 kB 168 kB
app-page-tur...dev.js gzip 315 kB 315 kB
app-page-tur..prod.js gzip 167 kB 167 kB
app-page.run...dev.js gzip 315 kB 315 kB
app-page.run..prod.js gzip 167 kB 167 kB
app-route-ex...dev.js gzip 70.8 kB 70.8 kB
app-route-ex..prod.js gzip 49.2 kB 49.2 kB
app-route-tu...dev.js gzip 70.8 kB 70.8 kB
app-route-tu..prod.js gzip 49.2 kB 49.2 kB
app-route-tu...dev.js gzip 70.4 kB 70.4 kB
app-route-tu..prod.js gzip 49 kB 49 kB
app-route.ru...dev.js gzip 70.4 kB 70.4 kB
app-route.ru..prod.js gzip 49 kB 49 kB
dist_client_...dev.js gzip 324 B 324 B
dist_client_...dev.js gzip 326 B 326 B
dist_client_...dev.js gzip 318 B 318 B
dist_client_...dev.js gzip 317 B 317 B
pages-api-tu...dev.js gzip 43.2 kB 43.2 kB
pages-api-tu..prod.js gzip 32.9 kB 32.9 kB
pages-api.ru...dev.js gzip 43.2 kB 43.2 kB
pages-api.ru..prod.js gzip 32.8 kB 32.8 kB
pages-turbo....dev.js gzip 52.5 kB 52.5 kB
pages-turbo...prod.js gzip 38.5 kB 38.5 kB
pages.runtim...dev.js gzip 52.5 kB 52.5 kB
pages.runtim..prod.js gzip 38.4 kB 38.4 kB
server.runti..prod.js gzip 62 kB 62 kB
Total 2.81 MB 2.81 MB ✅ -2 B
📎 Tarball URL
next@https://vercel-packages.vercel.app/next/prs/90542/next

@lukesandberg lukesandberg marked this pull request as ready for review February 26, 2026 00:15
@lukesandberg lukesandberg requested a review from a team February 26, 2026 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by: Turbopack team PRs by the Turbopack team. Turbopack Related to Turbopack with Next.js.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants