nextflow-io/nextflow

Cumulative job duration (realtime) in the nextflow execution report

Open

#6,298 opened on 2025年7月22日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)Groovy (3,382 stars) (784 forks)batch import
good first issuestale

説明

New feature

The nextflow execution report is a very helpful tool for profiling pipeline performance and resource allocation. The current report describes well the per-process distribution of runtimes, but does not report the cumulative realtime duration by process.

Use case

I have some process which run in reasonable amount of time, but are executed many thousands of times, leading to very large cumulative runtimes. These processes are great candidates for performance optimization, but do not stand out in the current report.

Suggested implementation

I currently derive this from the trace file, but it would be right at home as a cumulative runtime bar plot in a separate tab of the Job Duration section of the execution report.

コントリビューターガイド

技術スタック
groovy
領域
performancedata
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Familiarity with Nextflow execution reportBasic Groovy/Java knowledge
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
50
調査方針
Start by examining the existing execution report generation code, likely in the modules that produce HTML/plots. Look for the Job Duration section and how the current distribution plot is built. The cumulative duration bar plot could be added as a new tab following the same pattern. Consider leveraging the trace file parsing already present. Since no comments or PRs exist, the contributor should propose a design in the issue before coding.