We assume that you have an existing JMeter script
that you are already using professionally, and running it on conventional On-Premises or Cloud instances, likely on a high-performance server with many cores and a lot of memory, with many Virtual Users. We will show you how to modify
so that you can run it on many small Neocortix instances, rather than on one huge conventional server.
The key idea is to modify
so that it has at most 20 Virtual Users active at any time, and then you will need more instances to achieve the desired load. For example, if your
has 4000 Virtual Users active at its peak, you will modify it to have only 20 Virtual Users active, and use 200 Neocortix instances to achieve the desired load.
so that it has at most 20 Virtual Users active at any time, and make a note of the number of instances you will need to achieve your desired Load.
Please note that the Output File Name for the View Results Tree method should be set to
as shown here:
Please note also that the “Save as XML” checkbox should be unchecked in the JMeter Sample Result Save Configuration popup, so that the .jtl files will be in the right format, as shown here:
And then, finally, you will need to put
into a directory, like
, so that you can submit the directory to the Neocortix LoadTest tool. And you will also have to copy any other files into that directory that your script may need, like plugin .jar files, user.csv files, etc. Below we are showing the supporting files from the JPetStore example in the
JMeter Advanced tutorial