Scaling to a high number of inputs » History » Version 4
Luke Murphey, 09/22/2019 03:33 AM
| 1 | 2 | Luke Murphey | h1. Scale the Application to a High Number of Inputs |
|---|---|---|---|
| 2 | 1 | Luke Murphey | |
| 3 | 1 | Luke Murphey | h2. How many inputs can I run? |
| 4 | 1 | Luke Murphey | |
| 5 | 1 | Luke Murphey | A specific number is very difficult to identify since it is affected by several attributes (number of inputs, frequency of testing, memory, CPU, etc.). I have tested several hundred inputs on fairly low hardware with no issues. The app can scale very because it runs all of the inputs in a single process. |
| 6 | 3 | Luke Murphey | |
| 7 | 4 | Luke Murphey | h2. How do I prevent an excessive number if inputs after the host has been down? |
| 8 | 4 | Luke Murphey | |
| 9 | 3 | Luke Murphey | You may want to reduce the thread limit in order to avoid running an excessive number if inputs when the server is restarted after being down. |
| 10 | 4 | Luke Murphey | |
| 11 | 4 | Luke Murphey | h2. Does the app support SHC? |
| 12 | 4 | Luke Murphey | |
| 13 | 4 | Luke Murphey | The app is SHC aware and will only run the inputs on the SHC captain. |