Previously, ngrinder support process rampup. Because the process is very expensive resource, we could not make big size of processes. So the ramp up was very limited.
So we have recommended to use the thread ramp-up by putting the grinder.sleep(grinder.threadNumber * 1000) in the first execution of each test.
However this is not easy to understand and.. there are no way to find out how much threads are actually executing. Each thread is already executed from the view of controller and in the test running page, the threads count show always full executable thread count even though some threads are sleeping.
To solve this problem, we need to fix followings.
- Provide Process/Thread ramp-up selector in the perftest config page.
- Make the grinderengine's GrinderProcess be aware of these argument and do sleep threads depending on calculation and current thread number.
- Change ramp-up graph to be shown based on the thread count as well.
- Provide the vuser graph for comparison with TPS graph.