How to Initiate Tests Through Customer Intranet Nodes in AngusTester Cloud Service Version

Important Notice

Initiating load tests through intranet nodes enables precise evaluation of enterprise internal system performance while eliminating public network interference factors.

Environment Topology Analysis

• Public Network Load Test Flow

• Intranet Load Test Flow

Load Testing Mode Comparison:

Feature	Intranet Testing	Public Network Testing
Network Environment	Enterprise internal network	Public internet
Simulation Target	Internal user access behavior	External user access behavior
Latency Impact	< 5ms (negligible)	50-500ms (must be considered)
Applicable Systems	Internal management systems/API services/microservices	Portal websites/e-commerce platforms/public services
Performance Focus	Application processing capability/resource consumption	End-to-end experience/CDN effectiveness

Intranet Load Testing Scenarios

Internal System Validation	Precise Performance Evaluation	Special Environment Testing
- Enterprise Resource Planning (ERP) systems - Internal API gateway performance - Microservice call chain pressure - Database connection pool bottlenecks	- Eliminate public network fluctuations - Accurately reflect application processing capability - Infrastructure capacity planning - Middleware limit pressure testing	- Isolated network environment validation - Data security sensitive scenarios - Hybrid cloud architecture performance verification - Dedicated line network quality inspection

Intranet Load Testing Steps

Step 1: Add Intranet Node

1. Log in to AngusTester Console;
2. Navigate to Node Management > Add Node;
3. Fill in node identification information (recommended naming convention: BusinessDomain-Environment-Region).

Step 2: Install Node Agent

Install the node agent service following: AngusAgent Installation. "Online Installation" method is recommended.

Step 3: Node Status Verification

After successful installation, select the added node through AngusTester Execution->Create Execution->Advanced Parameters->Execution Nodes->Available Execution Nodes, then save the execution.

Intranet Load Testing Best Practices

Network Configuration Recommendations

1. Bandwidth Reservation
   ▸ Test traffic ≤ 70% of link bandwidth
   ▸ Recommended to configure QoS priority policies

2. Security Policies

   # Example: Open test ports
   iptables -A INPUT -p tcp --dport 8080-8090 -j ACCEPT

3. Topology Optimization
   ▸ Deploy testing nodes in same IDC as target systems
   ▸ Avoid firewall hop transitions

Data Analysis Key Points

• Network Latency Comparison: Intranet latency should stabilize at 1-5ms range
• Performance Baseline Establishment: TPS should increase 20%-50% compared to public network tests under same pressure
• Resource Consumption Analysis: Focus on CPU/memory/thread pool metrics

Start Cloud Service Load Testing Now: 🔗 Enter AngusTester Console 🔗 anslation maintains all technical accuracy while improving readability for international technical audiences, preserving the original Markdown structure and functionality.