jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From srijondas <>
Subject [GitHub] jmeter pull request #385: jMeter threads implemented using CachedThreadPool
Date Sun, 20 May 2018 22:48:07 GMT
GitHub user srijondas opened a pull request:

    jMeter threads implemented using CachedThreadPool

    ## Description
    <!--- Provide a general summary of your changes in the Title above -->
    <!--- Changed the method of multithreading in jMeter to CachedThreadPool, this is need
to pause and restart the threads, currently jMeter has no functionality to pause and restart
the threads once test execution has begun-->
    ## Motivation and Context
    <!--- Why is this change required? What problem does it solve? -->
    <!--- If it fixes an open issue, please link to the issue here. -->
    ## How Has This Been Tested?
    <!--- Tested using my local laptop using multiple threads -->
    <!--- Tested on my macbook, and I could see multiple threads running a http sampler-->
    <!--- Change affects the core functionality of jMeter, which is the multithreading
model used to generate load. -->
    ## Screenshots (if appropriate):
    ## Types of changes
    <!--- What types of changes does your code introduce? Delete as appropriate -->
    - New feature (non-breaking change which adds functionality)
    ## Checklist:
    <!--- Go over all the following points, and put an `x` in all the boxes that apply.
    <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help!
    - [ X] My code follows the [code style][style-guide] of this project.
    - [ ] I have updated the documentation accordingly.

You can merge this pull request into a Git repository by running:

    $ git pull 62390

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #385
commit 31ae054148a04e5b1a5cac3dead6e605d8902b8f
Author: Srijon <srijondas@...>
Date:   2018-05-20T22:40:51Z

    Fix to 62390



View raw message