id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
id
title
category
status
canonical_id
aliases
duplicate_of
source_trust_level
confidence_score
verification_status
tags
raw_sources
last_reinforced
github_commit
tech_stack
wiki-2026-0508-browser
Browser
10_Wiki/Topics
verified
self
Web Browser
Browser Internals
Rendering Engine
none
A
0.9
applied
browser
web
rendering
javascript
networking
2026-05-10
pending
language
framework
C++/Rust
Chromium/Gecko/WebKit
Browser
매 한 줄
"매 browser = networking stack + parsing + rendering + JS engine + sandbox 의 거대한 OS-like 시스템." . 매 2026 현재 Chromium-derived (Chrome, Edge, Brave, Arc) 가 ~70% market share, Firefox/Gecko 와 Safari/WebKit 이 나머지. 매 process-per-site isolation, GPU-accelerated compositing, V8 의 Sparkplug+Maglev+TurboFan tier 가 modern baseline.
매 핵심
매 multi-process architecture
Browser process : 매 UI, networking, IPC orchestration.
Renderer process : 매 site-per-process — Blink + V8.
GPU process : 매 compositing, WebGL/WebGPU.
Network service : 매 별도 process — credential isolation.
Utility processes : 매 audio, video decode, storage.
매 rendering pipeline
Parse HTML → DOM.
Parse CSS → CSSOM.
Style — match rules → ComputedStyle.
Layout — geometry computation.
Paint — layer 별 display list.
Composite — GPU 가 layer 합성.
매 JS engine tiers (V8)
Ignition (interpreter) → Sparkplug (baseline JIT) → Maglev (mid-tier) → TurboFan (optimizing JIT).
매 hot function 만 점진적 promotion.
매 응용
Web app development : 매 performance budgeting.
Extension / DevTools : 매 internal API.
Embedded webview : 매 Electron, Tauri, CEF.
Headless : 매 Puppeteer, Playwright scraping/test.
💻 패턴
Performance: Critical Rendering Path
Avoid layout thrash
Service worker — offline + cache
Intersection observer (lazy load)
Web Workers — off-main-thread
Performance API — measure real users
WebGPU compute (modern)
매 결정 기준
상황
Approach
Hydration TTI 느림
islands / partial hydration (Astro, Qwik)
Heavy compute on UI thread
Web Worker / WebAssembly
Repeated tiny renders
requestAnimationFrame batch
Need GPU for ML inference
WebGPU + ONNX Runtime Web
Cross-origin embed
iframe + CSP frame-ancestors
기본값 : HTTP/3 + service worker cache + defer non-critical JS + Web Vitals monitoring.
🔗 Graph
🤖 LLM 활용
언제 : web perf 최적화, browser API 선택, rendering pipeline 디버깅.
언제 X : server-side rendering 내부 (Node/Bun 영역).
❌ 안티패턴
document.write : 매 parser blocking — 절대 X.
Synchronous XHR : 매 main thread freeze — deprecated.
Layout thrash loop : 매 read-write 교차 → forced sync layouts.
Massive bundle (>1MB JS) : 매 mobile TTI 폭망 — code splitting 필수.
Too many compositor layers : 매 will-change 남발 → GPU memory exhaustion.
🧪 검증 / 중복
Verified (web.dev/architecture, Chromium design docs 2024, V8 blog 2025).
신뢰도 A.
🕓 Changelog
날짜
변경
2026-05-08
Phase 1
2026-05-10
Manual cleanup — multi-process arch, rendering pipeline, modern web APIs