Managing performance tests in NeoLoad requires more than just creating virtual users and launching scenarios. Sometimes, you need to fine-tune your test environment by enabling or disabling specific components—especially load generator nodes. Whether you’re troubleshooting, optimizing resource allocation, or rebalancing traffic, understanding how to disable a node in NeoLoad is an essential skill for any performance engineer.
TL;DR: Disabling a node in NeoLoad allows you to control load distribution, troubleshoot issues, or optimize test execution. You can disable a node directly from the Controller interface by modifying load generator settings in your test scenario. The process involves selecting the node, adjusting its status, and redeploying the updated configuration. Always verify node status before launching the test to avoid unintended load gaps.
What Is a Node in NeoLoad?
Before diving into the step-by-step process, it’s essential to understand what a node represents in NeoLoad.
In NeoLoad, a node typically refers to a Load Generator—a machine (physical or virtual) that executes virtual users during a performance test. Instead of running all traffic from a single machine, NeoLoad distributes load across multiple nodes to simulate real-world user activity more accurately.
There are generally two types of nodes:
- Local Load Generator – Installed on the same machine as the NeoLoad Controller.
- Remote Load Generator – Installed on separate machines to distribute load.
Disabling a node means preventing it from participating in a particular test execution without uninstalling or permanently removing it from NeoLoad.
Why Would You Disable a Node?
There are several real-world scenarios where disabling a node becomes necessary:
- Hardware maintenance – The machine requires updates or repairs.
- Network instability – Temporary connectivity problems.
- Load balancing adjustments – Redistributing virtual users.
- Cost optimization – Reducing cloud generator usage.
- Debugging – Isolating problematic traffic sources.
Instead of deleting the node configuration, which may require reinstallation later, disabling is a cleaner and reversible solution.
Pre-Checklist Before Disabling a Node
Before making changes, ensure the following:
- You have Administrator or appropriate access rights in NeoLoad.
- No critical test is currently running on the node.
- You understand how traffic distribution will be impacted.
- You’ve communicated changes with your team if working in a shared environment.
Preparation helps prevent execution errors and failed test runs.
Step-by-Step Guide to Disabling a Node in NeoLoad
Step 1: Open NeoLoad and Access the Controller
Launch NeoLoad and navigate to the Controller section, where test scenarios and load distribution are managed.
This interface allows you to configure:
- Virtual user populations
- Load policies
- Load Generators (nodes)
Step 2: Navigate to the Load Generators Panel
Within the Controller:
- Locate the Load Generators tab.
- View all configured nodes (local and remote).
- Check their current status (Connected, Disconnected, Ready, etc.).
NeoLoad displays useful details such as:
- Host name
- IP address
- Status
- Resource capacity
This overview gives insight into which nodes are active and healthy.
Step 3: Modify the Test Scenario Configuration
Disabling a node for a specific test involves adjusting scenario settings.
- Go to the Design tab (if necessary).
- Open your Test Scenario.
- Review how virtual users are distributed across load generators.
If the node is actively assigned virtual users, you must first reassign those users to another available generator.
Important: NeoLoad will not automatically redistribute traffic unless configured to do so.
Step 4: Remove or Uncheck the Node from the Scenario
To effectively disable a node from participating:
- Uncheck or deselect the node under the load distribution section.
- Alternatively, set its allocated virtual users to zero.
This ensures that no traffic will be executed from that node during the test.
Image not found in postmetaStep 5: Save and Validate Configuration
After making adjustments:
- Click Save.
- Run a validation check inside NeoLoad.
- Confirm that no virtual users are assigned to the disabled node.
Validation helps detect configuration inconsistencies before test execution.
Step 6: Verify Node Status
Go back to the Load Generators panel to confirm:
- The node shows no active assignment.
- Its status does not indicate active load.
You may optionally stop the Load Generator service on that machine for additional assurance.
Temporary Disable vs. Permanent Removal
It’s important to differentiate between disabling and removing a node.
| Action | What It Does | Reversible? | Best Use Case |
|---|---|---|---|
| Disable | Stops node from executing traffic | Yes | Maintenance or temporary suspension |
| Disconnect | Breaks communication with Controller | Yes | Network troubleshooting |
| Remove | Deletes node configuration | No (requires reconfiguration) | Permanent infrastructure changes |
For most operational needs, disabling is the safer choice.
Common Mistakes to Avoid
Even experienced performance testers sometimes overlook small details. Here are common pitfalls:
- Forgetting to reassign users – Leads to reduced overall load.
- Ignoring capacity limits – Other nodes may become overloaded.
- Skipping validation – Can cause runtime errors.
- Not updating documentation – Creates confusion in team environments.
Tip: Always compare expected total virtual users against assigned totals after disabling a node.
Best Practices for Managing Nodes in NeoLoad
Disabling nodes is only one part of effective load management. Consider these best practices:
1. Document Node Roles
Label nodes according to environment (e.g., staging, production simulation, API load).
2. Use Cloud Generators Wisely
If using cloud-based nodes, disable them when not in use to minimize costs.
3. Monitor Resource Utilization
Regularly check CPU and memory consumption before deciding to disable or redistribute.
4. Create Scalable Distribution Models
Design your test scenarios so they can flexibly accommodate disabled nodes without structural changes.
Troubleshooting Issues After Disabling a Node
Sometimes disabling a node may unintentionally affect test execution. Here’s how to resolve common issues:
- Test fails to launch: Revalidate scenario and confirm at least one node is active.
- Lower-than-expected throughput: Check if user redistribution was incomplete.
- Slow ramp-up: Remaining nodes may lack sufficient capacity.
Performance testing is a balancing act. Every infrastructure modification should be measured and monitored.
When Should You Re-Enable the Node?
You should consider re-enabling the node when:
- Maintenance is complete.
- Additional load capacity is required.
- You plan a high-scale performance or stress test.
- Geographical load simulation requires distributed traffic sources.
Re-enabling is straightforward—simply redistribute users to the node within the scenario and validate again.
Final Thoughts
Understanding how to disable a node in NeoLoad gives you greater control over your testing infrastructure. Rather than being locked into rigid configurations, you gain the flexibility to adapt to network issues, infrastructure upgrades, cost optimization efforts, and troubleshooting needs.
Performance testing isn’t just about generating traffic—it’s about managing resources strategically. By mastering node control in NeoLoad, you enhance reliability, reduce risk, and maintain realistic test simulations.
With careful planning, validation, and monitoring, disabling a node becomes a simple yet powerful tool in your performance testing toolkit.