Elixir & Phoenix: Scalable Backend Development · 강의

Elixir 벤치마킹과 프로파일링

벤치마킹 도구와 프로파일링 기법을 사용해 Elixir 코드의 성능 병목 지점을 찾아냅니다.

Elixir 벤치마킹과 프로파일링은(는) CoddyKit의 무료 Elixir & Phoenix: Scalable Backend Development 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Elixir & Phoenix: Scalable Backend Development 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Elixir & Phoenix: Scalable Backend Development 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Performance: Speed & Efficiency

In software development, performance refers to how fast and efficiently your application runs. It's crucial for a good user experience and managing server resources.

Slow applications can frustrate users, leading to abandonment. For backend systems, poor performance can mean higher infrastructure costs or an inability to handle user loads.

Responsiveness: How quickly the system responds to user input.
Throughput: How many operations it can handle over time.
Resource Usage: How much CPU, memory, or network it consumes.

What is Benchmarking?

Benchmarking is the process of measuring the performance of a piece of code or a system under specific conditions. It helps you understand how fast different parts of your code execute.

You often use benchmarking to compare different implementations of the same logic. For example, which way of processing a list is faster? By running them many times and averaging the results, you get reliable data.

Simple Manual Timing

Elixir provides basic tools to measure execution time. We can use System.monotonic_time/0 and System.convert_time_unit/3 to get a rough idea.

Let's try timing a simple list operation. The time is given in native units, then converted to microseconds.

defmodule MyTimer do
  def run_and_time(fun) do
    start_time = System.monotonic_time(:nanosecond)
    result = fun.()
    end_time = System.monotonic_time(:nanosecond)
    duration = System.convert_time_unit(end_time - start_time, :nanosecond, :microsecond)
    IO.puts "Function returned: #{inspect(result)}"
    IO.puts "Execution took: #{duration} µs"
  end

  def example_task do
    1..1_000_000 |> Enum.map(fn x -> x * 2 end)
  end
end

# To run this in an IEx session or script:
MyTimer.run_and_time(fn -> MyTimer.example_task() end)

Meet Benchee: Elixir's Benchmarker

While manual timing is useful, it's not robust enough for serious benchmarking. Factors like garbage collection, CPU load, and warm-up times can skew results.

Benchee is a popular Elixir library designed for accurate and reliable benchmarking. It runs your code many times, calculates statistics, and presents clear results.

Handles warm-up periods.
Performs statistical analysis (average, standard deviation).
Compares multiple functions easily.

First Benchee Benchmark

To use Benchee, you'd typically add {:benchee, "~> 1.0", only: :dev} to your mix.exs dependencies and run mix deps.get.

Here's how you define a simple benchmark. This code would usually be in a file like bench/my_benchmark.exs and run with mix bench.

defmodule MyBenchmarks do
  use Benchee.Benchmark

  def run do
    Benchee.run %{
      "list_sum" => fn -> Enum.sum(1..10_000) end
    },
    time: 1,
    memory_time: 0.1, # Shorten for quick example
    print: [fast_warning: false]
  end
end

# To run this directly (after adding Benchee to mix.exs and running mix deps.get):
# MyBenchmarks.run()

Comparing Implementations

One of Benchee's strengths is comparing different approaches. Let's benchmark two ways to append an element to a list: using ++ (concatenation) vs. [new_element | list] (prepense, then reverse if order matters).

For appending to the *end* effectively, ++ is common, but prepending is often faster. Benchee helps confirm this.

defmodule ListAppendBenchmarks do
  use Benchee.Benchmark

  def run do
    long_list = Enum.to_list(1..10_000)
    new_element = 10_001

    Benchee.run %{
      "append_with_++" => fn -> long_list ++ [new_element] end,
      "prepend_and_reverse" => fn -> [new_element | long_list] |> Enum.reverse() end
    },
    time: 1,
    memory_time: 0.1
  end
end

# ListAppendBenchmarks.run()

Deciphering Benchee Results

When Benchee runs, it outputs a table of statistics:

ips (iterations per second): How many times the function can execute in one second. Higher is better.
average: The average execution time per iteration. Lower is better.
std dev (standard deviation): How much the execution times vary. A lower standard deviation means more consistent results.
median: The middle value of all execution times.
memory usage: How much memory the operation consumes.

Focus on ips and average for speed, and std dev for consistency.

What is Profiling?

While benchmarking tells you how fast your code is, profiling tells you where your code is spending its time. It helps pinpoint specific functions or lines of code that are bottlenecks.

A profiler typically tracks:

CPU time: Which functions consume the most processing power.
Memory usage: Which parts allocate the most memory.
Function calls: The call stack, showing who calls whom.

This is crucial for optimizing, as you want to focus your efforts on the slowest parts.

Basic Profiling with :eprof

Elixir, running on the Erlang VM, has access to Erlang's powerful built-in profiler, :eprof. It helps you find CPU hotspots in your code.

You typically use :eprof interactively in an IEx session. It measures the execution time of functions called within a profiled block.

defmodule MyProfiledCode do
  def slow_function(n) do
    Enum.map(1..n, fn x -> :math.pow(x, 0.5) |> round end)
  end

  def entry_point do
    slow_function(5_000)
  end
end

# To profile in IEx:
# :eprof.start_profiling()
# MyProfiledCode.entry_point()
# :eprof.stop_profiling()
# :eprof.analyze()

Reading :eprof Reports

After running :eprof.analyze(), you'll get a report showing:

Function calls: How many times each function was called.
Total time: The total CPU time spent in that function and its children.
Self time: The CPU time spent directly in that function, excluding calls to other functions.

Look for functions with high 'self time' or 'total time' as potential bottlenecks. This indicates where the most work is being done.

Performance Tool Check

You've learned about both benchmarking and profiling. Now, let's test your understanding!

Summary: Optimize Your Code

Congratulations! You've explored essential tools for understanding and improving your Elixir application's performance.

Benchmarking (with Benchee) measures how fast code runs and compares different implementations.
Profiling (with :eprof) identifies where your code spends most of its time, pinpointing bottlenecks.

By using these techniques, you can write more efficient, faster, and scalable Elixir applications. Keep practicing to make performance analysis a regular part of your development workflow!

자주 묻는 질문

“Elixir 벤치마킹과 프로파일링” 강의는 무료인가요?

네 — “Elixir 벤치마킹과 프로파일링” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Elixir & Phoenix: Scalable Backend Development 강의 전체를 잠금 해제할 수 있습니다. Elixir & Phoenix: Scalable Backend Development 강의에는 총 4개의 강의가 포함되어 있습니다.

“Elixir 벤치마킹과 프로파일링”에서 뭘 배우나요?

벤치마킹 도구와 프로파일링 기법을 사용해 Elixir 코드의 성능 병목 지점을 찾아냅니다. 브라우저에서 직접 실행하는 실습 코드로 Elixir & Phoenix: Scalable Backend Development을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Elixir & Phoenix: Scalable Backend Development을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Elixir & Phoenix: Scalable Backend Development은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“Elixir 벤치마킹과 프로파일링” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Elixir & Phoenix: Scalable Backend Development 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Elixir & Phoenix: Scalable Backend Development 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Elixir & Phoenix: Scalable Backend Development(으)로 돌아가기