Release build of a large program needs more than 90 GB in scriptc-llvm-codegen, with no thread or memory limit

オープン
#3,613 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript

調査の方向性

This is a memory-profiling and design task, not a one-file edit. Start by reproducing the failure with the reported command on a large TypeScript program under a memory cap, then read the scriptc-llvm-codegen helper to find where it spawns one compile thread per hardware thread; the cached .bc/.o partitions under ~/.cache/scriptc/build/native-v1/partitions/<hash>/ show what a release partition produces. A first deliverable is a --jobs flag or SCRIPTC_CODEGEN_JOBS env var threaded through scriptc build, plus measurements of peak memory per thread at 4, 8 and 32 jobs. Done means the cap holds at a documented thread count and the option is in scriptc build --help.

索引モデルが issue の本文から書いたものです。

説明

A release build of a large program needs more than 90 GB of memory in scriptc-llvm-codegen, and there is no setting to lower its parallelism.

The program is the Paseo CLI (TypeScript; zod, commander and a WebSocket client among its dependencies), built on Linux x86-64 with 32 hardware threads and 123 GB of RAM:

scriptc build index.ts -o paseo --optimization release --no-keep-llvm --node-islands=off

Each build ran alone under a systemd memory cap (MemoryMax, MemorySwapMax=0), scriptc 0.4.10:

Optimization Cap Result
dev 40 GB killed
dev 48 GB built in 8 min
release 32 GB killed
release 60 GB killed, both with 32 CPUs and with 8 CPUs
release 90 GB killed in scriptc-llvm-codegen after 13 min, with 4 h 50 min of CPU time

The release cache directory (~/.cache/scriptc/build/native-v1/partitions/<hash>/) holds 191 .bc and 202 .o files, 3.4 GB in total, after these attempts.

The helper starts one compile thread per hardware thread. I have not measured how the peak splits between threads; the 8 CPU run at 60 GB failed too, so the thread count may not be the whole cause. I found no option, in scriptc build --help or in the helper, that limits threads or memory.

Requests:

  1. A way to set the number of codegen threads, for example --jobs or SCRIPTC_CODEGEN_JOBS, so a build can trade time for memory.
  2. If a release partition is expected to need several GB, a peak memory that does not grow with the thread count.

I can run a build with extra logging or a different scriptc version if that helps.

主要言語
TypeScript
スター
6.6k
フォーク
216
平均マージ
9時間 35分
マージ済み PR(30日)
775

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

vercel-labs/scriptc のほかの issue

vercel-labs/scriptc の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。