swiftui-performance-audit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SwiftUI Performance Audit

SwiftUI性能审计

Overview

概述

Audit SwiftUI view performance end-to-end, from instrumentation and baselining to root-cause analysis and concrete remediation steps.
端到端审计SwiftUI视图性能,从性能埋点和基准测试到根因分析及具体修复步骤。

Workflow Decision Tree

工作流决策树

  • If the user provides code, start with "Code-First Review."
  • If the user only describes symptoms, ask for minimal code/context, then do "Code-First Review."
  • If code review is inconclusive, go to "Guide the User to Profile" and ask for a trace or screenshots.
  • 如果用户提供代码,从「代码优先审查」开始。
  • 如果用户仅描述症状,请求提供最小化代码/上下文,然后进行「代码优先审查」。
  • 如果代码审查无法得出结论,进入「指导用户进行性能分析」环节,并请求提供跟踪数据或截图。

1. Code-First Review

1. 代码优先审查

Collect:
  • Target view/feature code.
  • Data flow: state, environment, observable models.
  • Symptoms and reproduction steps.
Focus on:
  • View invalidation storms from broad state changes.
  • Unstable identity in lists (
    id
    churn,
    UUID()
    per render).
  • Top-level conditional view swapping (
    if/else
    returning different root branches).
  • Heavy work in
    body
    (formatting, sorting, image decoding).
  • Layout thrash (deep stacks,
    GeometryReader
    , preference chains).
  • Large images without downsampling or resizing.
  • Over-animated hierarchies (implicit animations on large trees).
Provide:
  • Likely root causes with code references.
  • Suggested fixes and refactors.
  • If needed, a minimal repro or instrumentation suggestion.
收集:
  • 目标视图/功能代码。
  • 数据流:状态、环境、可观察模型。
  • 症状及复现步骤。
重点关注:
  • 大范围状态变更导致的视图无效化风暴。
  • 列表中的不稳定标识(
    id
    频繁变化、每次渲染生成
    UUID()
    )。
  • 顶层条件视图切换(
    if/else
    返回不同的根分支)。
  • body
    中的繁重操作(格式化、排序、图片解码)。
  • 布局抖动(深层栈、
    GeometryReader
    、偏好链)。
  • 未进行下采样或调整大小的大图片。
  • 过度动画的层级结构(大型树状结构上的隐式动画)。
提供:
  • 带有代码引用的可能根因。
  • 建议的修复和重构方案。
  • 必要时,提供最小化复现示例或埋点建议。

2. Guide the User to Profile

2. 指导用户进行性能分析

Explain how to collect data with Instruments:
  • Use the SwiftUI template in Instruments (Release build).
  • Reproduce the exact interaction (scroll, navigation, animation).
  • Capture SwiftUI timeline and Time Profiler.
  • Export or screenshot the relevant lanes and the call tree.
Ask for:
  • Trace export or screenshots of SwiftUI lanes + Time Profiler call tree.
  • Device/OS/build configuration.
说明如何使用Instruments收集数据:
  • 使用Instruments中的SwiftUI模板(Release构建)。
  • 复现精确的交互操作(滚动、导航、动画)。
  • 捕获SwiftUI时间线和时间分析器数据。
  • 导出或截图相关轨道和调用树。
请求提供:
  • 跟踪数据导出文件或SwiftUI轨道+时间分析器调用树的截图。
  • 设备/操作系统/构建配置信息。

3. Analyze and Diagnose

3. 分析与诊断

Prioritize likely SwiftUI culprits:
  • View invalidation storms from broad state changes.
  • Unstable identity in lists (
    id
    churn,
    UUID()
    per render).
  • Top-level conditional view swapping (
    if/else
    returning different root branches).
  • Heavy work in
    body
    (formatting, sorting, image decoding).
  • Layout thrash (deep stacks,
    GeometryReader
    , preference chains).
  • Large images without downsampling or resizing.
  • Over-animated hierarchies (implicit animations on large trees).
Summarize findings with evidence from traces/logs.
优先排查SwiftUI的常见问题:
  • 大范围状态变更导致的视图无效化风暴。
  • 列表中的不稳定标识(
    id
    频繁变化、每次渲染生成
    UUID()
    )。
  • 顶层条件视图切换(
    if/else
    返回不同的根分支)。
  • body
    中的繁重操作(格式化、排序、图片解码)。
  • 布局抖动(深层栈、
    GeometryReader
    、偏好链)。
  • 未进行下采样或调整大小的大图片。
  • 过度动画的层级结构(大型树状结构上的隐式动画)。
结合跟踪数据/日志中的证据总结发现。

4. Remediate

4. 修复优化

Apply targeted fixes:
  • Narrow state scope (
    @State
    /
    @Observable
    closer to leaf views).
  • Stabilize identities for
    ForEach
    and lists.
  • Move heavy work out of
    body
    (precompute, cache,
    @State
    ).
  • Use
    equatable()
    or value wrappers for expensive subtrees.
  • Downsample images before rendering.
  • Reduce layout complexity or use fixed sizing where possible.
应用针对性修复:
  • 缩小状态作用域(
    @State
    /
    @Observable
    更靠近叶子视图)。
  • 稳定
    ForEach
    和列表的标识。
  • 将繁重操作移出
    body
    (预计算、缓存、使用
    @State
    存储结果)。
  • 对昂贵的子树使用
    equatable()
    或值包装器。
  • 渲染前对图片进行下采样。
  • 降低布局复杂度,或在可能的情况下使用固定尺寸。

Common Code Smells (and Fixes)

常见代码异味(及修复方案)

Look for these patterns during code review.
代码审查时需注意以下模式。

Expensive formatters in
body

body
中的昂贵格式化器

swift
var body: some View {
    let number = NumberFormatter() // slow allocation
    let measure = MeasurementFormatter() // slow allocation
    Text(measure.string(from: .init(value: meters, unit: .meters)))
}
Prefer cached formatters in a model or a dedicated helper:
swift
final class DistanceFormatter {
    static let shared = DistanceFormatter()
    let number = NumberFormatter()
    let measure = MeasurementFormatter()
}
swift
var body: some View {
    let number = NumberFormatter() // 缓慢的内存分配
    let measure = MeasurementFormatter() // 缓慢的内存分配
    Text(measure.string(from: .init(value: meters, unit: .meters)))
}
建议在模型或专用辅助类中使用缓存的格式化器:
swift
final class DistanceFormatter {
    static let shared = DistanceFormatter()
    let number = NumberFormatter()
    let measure = MeasurementFormatter()
}

Computed properties that do heavy work

执行繁重操作的计算属性

swift
var filtered: [Item] {
    items.filter { $0.isEnabled } // runs on every body eval
}
Prefer precompute or cache on change:
swift
@State private var filtered: [Item] = []
// update filtered when inputs change
swift
var filtered: [Item] {
    items.filter { $0.isEnabled } // 每次body求值时都会运行
}
建议预计算或在输入变化时缓存结果:
swift
@State private var filtered: [Item] = []
// 当输入变化时更新filtered

Sorting/filtering in
body
or
ForEach

body
ForEach
中的排序/过滤

swift
List {
    ForEach(items.sorted(by: sortRule)) { item in
        Row(item)
    }
}
Prefer sort once before view updates:
swift
let sortedItems = items.sorted(by: sortRule)
swift
List {
    ForEach(items.sorted(by: sortRule)) { item in
        Row(item)
    }
}
建议在视图更新前完成排序:
swift
let sortedItems = items.sorted(by: sortRule)

Inline filtering in
ForEach

ForEach
中的内联过滤

swift
ForEach(items.filter { $0.isEnabled }) { item in
    Row(item)
}
Prefer a prefiltered collection with stable identity.
swift
ForEach(items.filter { $0.isEnabled }) { item in
    Row(item)
}
建议使用具有稳定标识的预过滤集合。

Unstable identity

不稳定标识

swift
ForEach(items, id: \.self) { item in
    Row(item)
}
Avoid
id: \.self
for non-stable values; use a stable ID.
swift
ForEach(items, id: \.self) { item in
    Row(item)
}
避免对非稳定值使用
id: \.self
;使用稳定的ID。

Top-level conditional view swapping

顶层条件视图切换

swift
var content: some View {
    if isEditing {
        editingView
    } else {
        readOnlyView
    }
}
Prefer one stable base view and localize conditions to sections/modifiers (for example inside
toolbar
, row content,
overlay
, or
disabled
). This reduces root identity churn and helps SwiftUI diffing stay efficient.
swift
var content: some View {
    if isEditing {
        editingView
    } else {
        readOnlyView
    }
}
建议使用一个稳定的基础视图,并将条件限制在局部区域/修饰符中(例如在
toolbar
、行内容、
overlay
disabled
中)。这会减少根标识的频繁变化,帮助SwiftUI的差异检测保持高效。

Image decoding on the main thread

主线程上的图片解码

swift
Image(uiImage: UIImage(data: data)!)
Prefer decode/downsample off the main thread and store the result.
swift
Image(uiImage: UIImage(data: data)!)
建议在主线程外完成解码/下采样,并存储结果。

Broad dependencies in observable models

可观察模型中的宽泛依赖

swift
@Observable class Model {
    var items: [Item] = []
}

var body: some View {
    Row(isFavorite: model.items.contains(item))
}
Prefer granular view models or per-item state to reduce update fan-out.
swift
@Observable class Model {
    var items: [Item] = []
}

var body: some View {
    Row(isFavorite: model.items.contains(item))
}
建议使用细粒度视图模型或每个项目的独立状态,以减少更新扩散范围。

5. Verify

5. 验证

Ask the user to re-run the same capture and compare with baseline metrics. Summarize the delta (CPU, frame drops, memory peak) if provided.
请求用户重新运行相同的捕获操作,并与基准指标进行比较。 如果用户提供数据,总结差异(CPU占用、掉帧数、内存峰值)。

Outputs

输出内容

Provide:
  • A short metrics table (before/after if available).
  • Top issues (ordered by impact).
  • Proposed fixes with estimated effort.
提供:
  • 简短的指标表格(如有前后对比数据)。
  • 按影响优先级排序的主要问题。
  • 带有预估工作量的修复方案。

References

参考资料

Add Apple documentation and WWDC resources under
references/
as they are supplied by the user.
  • Optimizing SwiftUI performance with Instruments:
    references/optimizing-swiftui-performance-instruments.md
  • Understanding and improving SwiftUI performance:
    references/understanding-improving-swiftui-performance.md
  • Understanding hangs in your app:
    references/understanding-hangs-in-your-app.md
  • Demystify SwiftUI performance (WWDC23):
    references/demystify-swiftui-performance-wwdc23.md
将用户提供的苹果文档和WWDC资源添加到
references/
目录下。
  • 使用Instruments优化SwiftUI性能:
    references/optimizing-swiftui-performance-instruments.md
  • 理解并改进SwiftUI性能:
    references/understanding-improving-swiftui-performance.md
  • 理解应用卡顿问题:
    references/understanding-hangs-in-your-app.md
  • 揭秘SwiftUI性能(WWDC23):
    references/demystify-swiftui-performance-wwdc23.md