Skip to content

⚡ Bolt: Gantt 차트 렌더링 성능 최적화 - #330

Closed
seonghobae wants to merge 2 commits into
developfrom
bolt-gantt-chart-rendering-15319300219068221064
Closed

⚡ Bolt: Gantt 차트 렌더링 성능 최적화#330
seonghobae wants to merge 2 commits into
developfrom
bolt-gantt-chart-rendering-15319300219068221064

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

💡 What
app.js에서 간트 차트의 테이블(createGanttMetaTable, createGanttChartTable)을 렌더링할 때 반복문 안에서 무수히 많은 노드를 생성하던 document.createElement 호출을, 미리 선언한 템플릿 노드를 .cloneNode(false)로 복제하는 방식으로 교체했습니다.

🎯 Why
테이블의 각 행(row), 셀(cell), 트랙(track) 등 수백~수천 개의 DOM 요소를 document.createElement로 동적 생성하면 JavaScript와 C++엔진 사이의 오버헤드가 누적되며 성능 병목을 일으킬 수 있습니다. 특히 O(N) 렌더링 루프에서 이 방식은 심각한 자원 낭비를 유발하므로 정적 템플릿 복제 방식으로 최적화했습니다.

📊 Impact
간트 차트의 행, 셀 생성 시 소모되는 DOM 할당 비용과 메모리 오버헤드가 크게 줄어, 작업이 많은 대규모 WBS에서도 간트 렌더링 시간이 현저히 단축됩니다.

🔬 Measurement

  • Playwright E2E 테스트가 여전히 통과되는지 확인 (pnpm run test:e2e).
  • 대량의 태스크를 화면에 추가한 후, '간트 보기' 버튼을 눌렀을 때 차트 렌더링이 더 매끄럽고 빠르게 수행되는지 시각적으로 검증합니다.

PR created automatically by Jules for task 15319300219068221064 started by @seonghobae

- `document.createElement`를 여러 번 반복 호출하는 O(N) DOM 생성 루프를 개선하기 위해 `cloneNode(false)`를 활용하여 정적 템플릿 요소를 복제하는 방식을 도입했습니다. 이를 통해 JS-to-C++ 간의 메모리 할당 및 가비지 컬렉션 부하를 크게 줄였습니다.
- 관련 함수: `createGanttMetaTable`, `createGanttChartTable`
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

- `document.createElement`를 여러 번 반복 호출하는 O(N) DOM 생성 루프를 개선하기 위해 `cloneNode(false)`를 활용하여 정적 템플릿 요소를 복제하는 방식을 도입했습니다. 이를 통해 JS-to-C++ 간의 메모리 할당 및 가비지 컬렉션 부하를 크게 줄였습니다.
- 관련 함수: `createGanttMetaTable`, `createGanttChartTable`

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head f71d3b81320788c20a652b68f6a0866acc379fae.

  • Head SHA: f71d3b81320788c20a652b68f6a0866acc379fae

  • Workflow run: 29594527349

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: f71d3b81320788c20a652b68f6a0866acc379fae
  • Workflow run: 29594527349
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head f71d3b81320788c20a652b68f6a0866acc379fae.

  • Head SHA: f71d3b81320788c20a652b68f6a0866acc379fae

  • Workflow run: 29594527349

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

@seonghobae

Copy link
Copy Markdown
Contributor Author

Closing as obsolete duplicate in the PR queue cleanup. Keep latest candidates: #386 (security hono+CSV), #385 (focus restore), #384 (padStart), #381/#380 (analytics), #367 (playwright). Prefer landing one green PR per theme over stacked Jules/agent clones.

@seonghobae seonghobae closed this Jul 31, 2026
@google-labs-jules

Copy link
Copy Markdown

Closing as obsolete duplicate in the PR queue cleanup. Keep latest candidates: #386 (security hono+CSV), #385 (focus restore), #384 (padStart), #381/#380 (analytics), #367 (playwright). Prefer landing one green PR per theme over stacked Jules/agent clones.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant