ISO8583 Simulator resources needed for Functional, regression and Performance testing
Functional Testing with UI.
The most common scenarion id Functional Testing, where the user is updating test cases, running tests manually, intepreting results and re-testing.
The most common OS for this is Windows, although Ubbuntu and MacOS would do just fine, assuming the correct java version is installed.
Assuming the OS requires for itself 8 vcpus and 8 GB RAM, the simulator would work fine with this configuration,
Ideally it would get another 2 vcpus an/or 2 GB RAM for smooth operation under simnple Functional testing.
If the user would be creating regressions of hundreds or thousands of test cases, then 4 vcpus and 4 GB RAM, on top of the OS requirements, would make operating it smoother.
Functional testing in console mode
When running the ISO8583 simulator in console mode, the common scneario would be to have it running as an issuer, all the time.
Then, a minimum 1VCPU and 1 GB RAM will be enough for moderate use on a light OS, like CentOS. For Ubuntu, add 1vcpu and 1GB RAM.
If using the OS with UI, like Windows and Ubuntu, then add 1VCPU and 1GB ram on top of what the OS requires.
Regression testing in console mode
When running Regression Testing with the simulator in console mode, the common scneario would be to have it running as an acquirer, to execute a specific regression set
Then, a minimum 2VCPU and 2 GB RAM will be enough for moderate use on a light OS, like CentOS. For Ubuntu, add 1 VCPU and 1GB RAM.
If using the OS with UI, like Windows and Ubuntu, then add 1VCPU and 1GB ram on top of what the OS requires.
CICD mode
When running the simulator in CICD mode, the smallest agent that can run java 1.8 will be enough.
Performace testing/Load testing
For ISO8583 high performance testing, a high performance VM is advised, preferably 16 VCPUs and 16 GB RAM on Windows with UI.
in Load test mode, the lack of resources will seriously imact the performance of the tests, as the simulator will use a lot of resources in a very short period of time, not giving a lot of time to the OS to optimize.
When executing performance Testing, the simulator will continously monitor its own perfrmance and give isights over how much faster it can go, and give errors if it can not go at the required speed, with the current resources.
