The Timer Client model – a solution?
One solution to this problem is to dedicate a single machine to the measuring of response times. I call this the “timer client” model. As of The Grinder 2.6.1 you can set a property (grinder.recordTime for The Grinder 2, renamed to grinder.reportTimesToConsole for The Grinder 3) to be false which will cause the worker processes that use that grinder.properties file not report the test times to the console. You should run all but one of your worker processes with this property set to false. These are the load clients. You should copy the grinder.properties file to a dedicated timer client machine, change the grinder.recordTime/grinder.reportTimesToConsole property to be true, and set grinder.processes and grinder.threads to 1. The single worker process will run on the timing client, record all timing information and (optionally) report it to the console. The less other stuff you run on the timing client, the better. The disadvantage of this method is that the statistical sample of the t
Related Questions
- For most of our users, a client server solution is fine. However, is it possible for remote brokers and distributors to perform restricted sales and stock management via the web?
- The BRMS Application Client overview states the solution is being limited to user data. Why can I backup my entire system to the TSM server?
- The Timer Client model - a solution?
