What disabling a node means in Neoload

Disabling a node in Neoload means temporarily stopping that machine from running any part of your load test without removing it from your test setup. When you disable a node, Neoload skips it during test execution — the load that would have run on that node gets redistributed to your remaining active nodes, or the test straightforward runs with less total load. The node stays in your configuration and can be re-enabled later without reconfiguring anything.

This is different from deleting a node, which removes it from your setup entirely. Disabling is useful when a machine needs maintenance, when you want to test how your system performs with fewer load generators, or when a node is having temporary problems you plan to fix.

Key Takeaways

  • Disabling a node removes it from the current test run but keeps it saved in your configuration for later use.
  • You disable a node through the Machines section of the Neoload interface, by unchecking the node or using the disable option in the context menu.
  • Load that would have run on a disabled node either redistributes to active nodes or reduces your total test load, depending on how your test is configured.
  • A disabled node can be re-enabled at any time without losing any of its settings or connection details.

Where to find the disable option

Open Neoload and go to the Machines section in the left panel. This shows all the nodes you have set up — both local machines and remote load generators. Find the node you want to disable in this list.

Right-click on the node name and look for a "Disable" or "Disable Machine" option in the menu that appears. Some versions of Neoload also let you uncheck a checkbox next to the node name to disable it. The exact wording and location can vary slightly between Neoload versions, but the Machines section is always where you manage which nodes are active.

What happens to your load when you disable a node

When you disable a node, Neoload needs to decide what to do with the load that was assigned to run on that machine. If your test is set to distribute load evenly across all nodes, disabling one node means the remaining active nodes will each take on a larger share of the total load to compensate.

If your test has specific load assignments — for example, "Node A runs 50 users and Node B runs 30 users" — then disabling Node A means only Node B runs, and your total test load drops to 30 users. The behavior depends on how you configured your load distribution when you built the test. Check your test's load configuration if you need to know exactly what will happen.

Re-enabling a disabled node

To turn a disabled node back on, return to the Machines section and right-click the disabled node again. Select "Enable" or check the checkbox next to its name. The node will be active again the next time you run a test, and all its settings — connection details, IP address, port, and any other configuration — remain exactly as they were.

You do not need to reconfigure anything or re-enter credentials. Neoload remembers the node's setup while it is disabled, so re-enabling is when ready.

When to disable instead of delete

Disable a node when you plan to use it again soon or when you are troubleshooting. For example, if a load generator machine needs a software update, disable it, perform the update, and re-enable it. If you want to test how your process performs under lighter load, disable some nodes temporarily to see the difference.

Delete a node only when you no longer need it and have no reason to keep its configuration. Disabling is the safer choice because it preserves everything about that node and takes only a few seconds to reverse.

Checking which nodes are active before you run a test

Before you start a test, look at the Machines section one more time to confirm which nodes are enabled. Neoload usually shows enabled nodes with a checkmark or a different visual indicator — often a green dot or an "enabled" label — while disabled nodes appear grayed out or marked as "disabled."

This quick check prevents the mistake of running a test with fewer nodes than you intended. If you see a node you thought was active but it is disabled, you can re-enable it right then before starting the test.

Frequently Asked Questions

Does disabling a node stop a test that is already running?

No. Disabling a node only affects future test runs. If a test is currently executing, disabling a node during that run does not stop the test or remove that node from the active test. You must stop the test first, then disable the node, then start a new test run.

Can I disable a node if it is currently being used in a test?

You can disable it in the configuration, but Neoload will not remove it from an active test that is already running. Stop the test first, disable the node, and then start a fresh test run to see the effect of the disabled node.

Will disabling a node affect my test results or data?

Disabling a node changes how much load your test generates, which will affect your results — you will see lower response times and throughput because fewer machines are generating load. The test results themselves are not deleted or corrupted; they straightforward reflect the lighter load from fewer active nodes.

What if I disable a node and forget to re-enable it before my next test?

Your test will run without that node, and you may not notice when ready if you are not paying attention to the Machines section. Always check which nodes are enabled before starting a test, especially if you disabled something for maintenance and meant to turn it back on.