[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[pmouawad <gi...@git.apache.org>]

Github user pmouawad commented on the issue:

    https://github.com/apache/jmeter/pull/231
  
    Hi @vlsi ,
    Could you confirm your component implements the following features:
    1) "Specific number of iterations per hour".
       The very basic requirement is to ensure you end up exactly 50
    iterations per hour.
       Business customers would not understand if you report load test
    results with 47 executions "just because the random was random".
    
       All timers except "Constant" can easily send excessive requests or
    send less requests than required. There is no way to control it.
    
    2) "Bursty load" simulation. There is no easy way to test "50
    iterations per hour as 10 bursts of 5 items".
    
    3) "Repeatable test profile". All the random timers produce different
    pattern on each test run. This is not good for low-level analysis
    (e.g. compare of CPU% charts, etc).
    
    4) "Avoid all thread groups" to fire at 00:00:00. By default, all
    thread groups would fire at 0, so there would be noticeable spike at
    the start of the test.
    
    Thanks


---