Load Testing & Performance Benchmarking (JMeter & k6) · レッスン

現実的なワークロードの設計

多様なユーザー行動とビジネスプロセスを正確に反映する、高度なワークロードモデルを設計します。

「現実的なワークロードの設計」はCoddyKit上の無料Load Testing & Performance Benchmarking (JMeter & k6)レッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはLoad Testing & Performance Benchmarking (JMeter & k6)学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Load Testing & Performance Benchmarking (JMeter & k6)コースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

The Art of Realistic Workloads

Welcome to "Crafting Realistic Workloads"! In performance testing, a workload model defines how virtual users interact with your system during a test.

It's crucial because a realistic model ensures your test results accurately predict how your system will perform under real-world conditions, helping you find actual bottlenecks.

Defining Your Virtual Users

Start by identifying your user personas. Who uses your application? (e.g., guest, registered user, administrator). Each persona might have different behaviors.

Then, map out their typical business processes or "user journeys." What steps do they take? (e.g., "Guest browses products," "Registered user adds to cart and checks out").

Balancing Actions and Operations

A transaction mix describes the proportion of different actions users perform. For example, 70% of users might browse, 20% search, and only 10% make a purchase.

This mix should reflect real-world usage patterns, often derived from analytics data or business requirements, to accurately simulate system load.

The Importance of Think Time

Think time (or pacing) is the pause a real user takes between actions. Without it, virtual users send requests as fast as possible, which is unrealistic and can overwhelm the system.

Adding realistic delays simulates human interaction, making your load test more accurate and preventing premature bottlenecks.

Shaping Your Load Profile

A load test typically has three phases: ramp-up, steady-state, and ramp-down.

Ramp-up: Gradually increases the number of virtual users.
Steady-state: Maintains a constant peak load for a duration.
Ramp-down: Gradually decreases the number of virtual users.

These phases simulate how user load changes over time in the real world.

Dynamic Data for Unique Users

For a truly realistic workload, each virtual user should use unique, varied data. This prevents caching effects from skewing results and simulates diverse user inputs.

Instead of logging in with "user1" repeatedly, simulate multiple users like "user1", "user2", "user3", each with their own unique data set for actions.

Sourcing Real-World Insights

Where do you find the data to build your workload model?

Web Analytics: Tools like Google Analytics provide user behavior patterns.
Server Logs: Access logs reveal request frequencies and popular endpoints.
Business Intelligence: Reports on sales, user activity, etc.
Product Owners/Managers: Direct insights into expected user journeys and peak usage.

JMeter: Throughput Controller

In JMeter, the Throughput Controller is excellent for defining a transaction mix. It allows you to specify a percentage of executions for its child elements.

For example, you can have one controller for "Browse Products" with 70% throughput and another for "Checkout" with 10% throughput, reflecting your desired mix.

k6: Defining Multiple Scenarios

k6's scenarios block is powerful for modeling diverse user behaviors. You can define multiple scenarios, each with its own executor, VUs, and duration, to simulate complex workloads.

Here's an example simulating different user types with distinct load patterns:

import http from 'k6/http';
import { sleep } from 'k6';

export const options = {
  scenarios: {
    browserUser: {
      executor: 'constant-vus',
      vus: 10,
      duration: '30s',
      exec: 'browserUserFlow', // function to execute
      tags: { type: 'browser' },
    },
    apiUser: {
      executor: 'ramping-vus',
      startVUs: 0,
      stages: [
        { duration: '10s', target: 5 },
        { duration: '20s', target: 5 },
        { duration: '5s', target: 0 },
      ],
      exec: 'apiUserFlow', // function to execute
      tags: { type: 'api' },
    },
  },
};

export function browserUserFlow() {
  http.get('https://test.k6.io/public/croco-products/');
  sleep(5);
  http.get('https://test.k6.io/news.php');
  sleep(3);
}

export function apiUserFlow() {
  http.get('https://test-api.k6.io/public/croco/1');
  sleep(1);
}

Realistic Workload Components

Which of the following are essential components when designing a realistic workload model for performance testing? (Select all that apply)

Recap: Crafting Realistic Loads

In this lesson, we explored the critical elements of crafting realistic workload models for performance testing.

We covered defining user personas, business processes, and transaction mix.
We emphasized the importance of pacing, concurrency patterns, and dynamic data.
Finally, we looked at how to implement these models using tools like JMeter and k6.

A well-designed workload is the foundation for meaningful performance test results!

よくある質問

「現実的なワークロードの設計」レッスンは無料ですか？

はい。「現実的なワークロードの設計」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Load Testing & Performance Benchmarking (JMeter & k6)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Load Testing & Performance Benchmarking (JMeter & k6)コースには全4レッスンが含まれています。

「現実的なワークロードの設計」で何を学びますか？

多様なユーザー行動とビジネスプロセスを正確に反映する、高度なワークロードモデルを設計します。ブラウザで直接実行するハンズオンコードでLoad Testing & Performance Benchmarking (JMeter & k6)を演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Load Testing & Performance Benchmarking (JMeter & k6)を始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのLoad Testing & Performance Benchmarking (JMeter & k6)は初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「現実的なワークロードの設計」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このLoad Testing & Performance Benchmarking (JMeter & k6)レッスンでコードを書いて実行できますか？

はい。すべてのLoad Testing & Performance Benchmarking (JMeter & k6)レッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Load Testing & Performance Benchmarking (JMeter & k6)に戻る