Customer Cases
Pricing

How to Enhance Performance Tests with Custom Network Scenarios

LEARN HOW TO CREATE CUSTOM NETWORK SCENARIOS TO ENHANCE YOUR PERFORMANCE TESTING AND IMPROVE YOUR APPLICATION'S USER EXPERIENCE

Why Customize Network Scenes?

Customizing network scenes allows you to simulate different network conditions, such as latency, delay jitter, packet loss, bandwidth limitations, and more. By testing your application under these varied conditions, you can identify potential performance issues and optimize your application accordingly.

Two Ways to Customize Network Scenarios

PerfDog offers two methods to set up customized network scenarios:

1. Scene Template: This method automatically generates corresponding parameters based on the selected region and scene.

2. Custom Template: This method requires manual input of each network parameter.

Scene Template

The scene template consists of two sections

1. Region and Network Type: After selecting the desired region and network type, PerfDog provides information on delay and packet loss rate. This data simulates network conditions between different regions.

2. Scene: Each scene corresponds to different weak network parameters, simulating specific network environments.

Custom Template

The custom template allows you to manually control various network parameters:

1. Network Bandwidth: This parameter controls the upstream and downstream network speed and the length of the statistical IP packet. The unit used is kilobits per second, equivalent to 125 bytes per second.

2. Network Delay: This parameter adds a fixed delay to upstream and downstream IP packets, measured in milliseconds.

3. Delay Jitter: This parameter allows you to set two variables for uplink and downlink, namely delay and probability. The probability parameter determines the likelihood of the delay taking effect, while the delay parameter increases the maximum value of delay.

4. Random Packet Loss: This parameter sets the probability of random discarding of upstream and downstream IP packets.

5. Weak Network Type: This parameter includes "complete packet loss" and "Burst," two different weak network models. You can specify the release duration and weak network duration, which determine when the weak network model takes effect.

6. Protocol Control: This parameter ensures that only the IP packets of the selected protocol will be affected by the weak network parameters, while the rest will be forwarded directly.

7. Weak Network IP: This parameter allows you to specify that only IP packets sent to or from the filled-in IP will be affected by the weak network parameters, while packets from other sources will be forwarded directly.

PD网络测试推广
Latest Posts
1LLM-Driven Intelligent Testing: Core Concepts, RAG Integration, and Advanced Scenarios Explore the deep integration of Large Language Models (LLMs) in intelligent testing. Learn how RAG and AI Agents revolutionize requirement analysis, test case generation, root cause analysis, and strategy optimization.
2Intelligent Testing System: Enterprise Implementation Path & Trends 2026 A complete guide to intelligent testing system, covering 5-layer architecture, 4 core modules, enterprise implementation path, team building & real cases for quality, efficiency & cost reduction.
3Shift Left Testing & Shift Right Testing: Building a Full-Lifecycle Quality Assurance System Discover the core principles, implementation practices, and enterprise case studies of Shift Left Testing and Shift Right Testing. Learn how to build a full-lifecycle intelligent quality assurance system to reduce defects and ensure production stability.
4Low-Code/No-Code Testing Platform Practices: Mabl, Testim, Applitools Guide Explore low-code/no-code testing practices with Mabl, Testim, Applitools. Learn core concepts, practical operations, enterprise implementation strategies, and how to improve testing efficiency significantly.
5Cloud-Native Testing: Strategies for Containerized & Distributed Environments Cloud-native testing guide for testers: Learn container (Docker) & microservice testing strategies, tools (Sentinel, SkyWalking), real cases, and pitfalls to ensure distributed system stability in 2026.