Electron Desktop App Development · Pelajaran

Pembuatan Profil Kinerja

Gunakan alat bawaan dan utilitas eksternal untuk membuat profil kinerja aplikasi Electron, menemukan hambatan kinerja dan area yang perlu diperbaiki.

Pembuatan Profil Kinerja adalah pelajaran Electron Desktop App Development gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Electron Desktop App Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

What is Performance Profiling?

Performance profiling is like giving your Electron app a health check! It's the process of analyzing your app's resource usage (CPU, memory, network) to find out where it's slowing down.

For desktop apps, a smooth, responsive user experience is key. Profiling helps us pinpoint bottlenecks and make our apps feel snappy.

Pinpointing Common Bottlenecks

Electron apps combine web tech with Node.js, meaning slowdowns can come from many places:

UI Rendering: Complex animations or heavy DOM manipulation.
Heavy JavaScript: Long-running scripts blocking the UI.
IPC Overhead: Too much communication between main and renderer processes.
Memory Leaks: Unreleased objects consuming more and more RAM.
Disk I/O: Slow file reads/writes in the main process.

DevTools for Renderer Process

Since the Electron renderer process is essentially a Chromium web page, you can use the familiar Chromium Developer Tools! These are essential for debugging and profiling your UI.

To open DevTools for a window, use myWindow.webContents.openDevTools(); in the main process.

Profiling Renderer CPU Usage

Open DevTools (Ctrl+Shift+I or Cmd+Option+I) and navigate to the Performance tab. Click the record button, interact with your UI, then stop recording.

Look for flame charts and identify long tasks that block the main thread. Here's an example of a CPU-intensive renderer script:

/*
This code runs in the renderer process (e.g., in index.html).
It's a snippet, not a full standalone program.
*/

function performHeavyTask() {
  console.log('Starting heavy renderer task...');
  let sum = 0;
  for (let i = 0; i < 50000000; i++) { // 50 million iterations
    sum += Math.sqrt(i);
  }
  console.log('Heavy renderer task finished:', sum);
  return sum;
}

// Example usage: call this function on a button click
// document.getElementById('myButton').addEventListener('click', performHeavyTask);

Profiling Renderer Memory

The Memory tab in DevTools is crucial for finding memory leaks. You can take "Heap snapshots" to see objects currently in memory, or record an "Allocation timeline" to track memory usage over time.

A common leak is holding onto references to detached DOM elements. Here's a simple example that allocates memory:

/*
This code runs in the renderer process (e.g., in index.html).
It's a snippet, not a full standalone program.
*/

let memoryHog = [];

function allocateMoreMemory() {
  console.log('Allocating more memory...');
  for (let i = 0; i < 10000; i++) {
    memoryHog.push({
      id: i,
      data: new Array(1000).fill('some long string to consume memory')
    });
  }
  console.log('Current memoryHog size:', memoryHog.length);
}

// Example usage: call this function repeatedly
// document.getElementById('allocateBtn').addEventListener('click', allocateMoreMemory);

Node.js Inspector for Main

The main process is a Node.js environment. To profile it, we use the Node.js Inspector, which is compatible with Chrome DevTools!

You start your Electron app with the --inspect flag, then connect DevTools to the provided URL (usually chrome-devtools://...) via chrome://inspect in your Chrome browser.

Profiling Main Process CPU/Mem

After connecting DevTools to your main process, you'll see a DevTools instance specifically for Node.js. Use the Profiler tab for CPU flame graphs and the Memory tab for heap snapshots, just like with the renderer.

Run this example as a Node.js script and try connecting DevTools to profile its CPU usage:

// main_process_profiling_example.js
// To run: node --inspect main_process_profiling_example.js
// Then open chrome://inspect in Chrome and click "Open dedicated DevTools for Node"

function calculateHeavySum() {
  console.log('Starting heavy main process task...');
  let sum = 0;
  for (let i = 0; i < 200000000; i++) { // 200 million iterations
    sum += Math.sin(i) * Math.cos(i);
  }
  console.log('Heavy main process task finished:', sum);
  return sum;
}

console.log("Main process example started.");
// Simulate a recurring task or an event that triggers heavy work
setTimeout(() => {
  const result = calculateHeavySum();
  console.log("Result of heavy calculation:", result);
}, 1000);

// Keep the process alive for a bit for inspection
setInterval(() => {
  // console.log("Main process still running...");
}, 5000);

// This is a standalone Node.js program entry point.

Interpreting Profiling Data

Once you have a profile, the real work begins! Look for:

Flame Charts: Visualize call stacks over time. Wider bars mean more time spent. Look for "hot paths" (functions called frequently or taking long).
Call Tree/Bottom-Up: Shows functions by total time, helping identify the most expensive operations.
Memory Snapshots: See object counts, sizes, and retained sizes to spot leaks.

Beyond DevTools: External Tools

For deeper, system-level performance analysis, you might need tools outside of DevTools:

Linux: perf for CPU and kernel-level profiling.
macOS: Instruments for comprehensive system performance analysis.
Windows: Windows Performance Recorder (WPR) for detailed system activity.

These are advanced tools, but good to know exist for tough performance issues.

Choosing the Right Profiling Tool

You suspect your Electron application's UI is occasionally freezing, and memory usage keeps climbing slowly over time. Which two tools/methods would be most effective for investigating these issues?

Recap: Performance Profiling

Great job! You've learned how to approach performance profiling in Electron:

Use Chromium DevTools for both renderer (UI/JS) and main (Node.js) processes.
Focus on the Performance tab for CPU usage and UI responsiveness.
Utilize the Memory tab for identifying memory leaks and excessive allocations.
Understand how to interpret flame charts and memory snapshots.

Profiling is key to building fast, reliable Electron applications!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pembuatan Profil Kinerja” gratis?

Ya — teks lengkap “Pembuatan Profil Kinerja” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Electron Desktop App Development, upgrade ke CoddyKit PRO. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pembuatan Profil Kinerja”?

Gunakan alat bawaan dan utilitas eksternal untuk membuat profil kinerja aplikasi Electron, menemukan hambatan kinerja dan area yang perlu diperbaiki. Kamu berlatih Electron Desktop App Development dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Electron Desktop App Development?

Tidak diperlukan pengalaman sebelumnya. Electron Desktop App Development di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.

Berapa lama pelajaran “Pembuatan Profil Kinerja” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Electron Desktop App Development ini?

Ya. Setiap pelajaran Electron Desktop App Development menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Electron Desktop App Development