GitHub user pmouawad opened a pull request:

    https://github.com/apache/jmeter/pull/135

    Bug 59034 - Parallel downloads connection management is not realistic

    Draft of a patch making parallel downloads more realistic by sharing the 
HttpClient instance between Main browser thread and threads used to download 
embedded resources.
    This will allow Keep Alive and connection reuse accross downloads.

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

    $ git pull https://github.com/pmouawad/jmeter BUG_59034

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

    https://github.com/apache/jmeter/pull/135.patch

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

    This closes #135
    
----
commit a7d5470fa49659fa3ea895b75f522b0bca70fc88
Author: Philippe M <[email protected]>
Date:   2016-02-21T15:14:57Z

    Bug 59034 - Parallel downloads connection management is not realistic
    
    no need to close httpclient instance for child threads

commit abd0646a3cb65e883b95c3a02899150ae54b4d6d
Author: Philippe M <[email protected]>
Date:   2016-02-21T15:17:01Z

    Bug 59034 - Parallel downloads connection management is not realistic
    
    Share HttpClient with child threads so that parallel download uses same 
HttpClient as the parent thread(user thread)

commit 5939c8840f87880b12d9c8412e019dd2af26575d
Author: Philippe M <[email protected]>
Date:   2016-02-21T15:20:05Z

    Bug 59034 - Parallel downloads connection management is not realistic
    
    Increase  Max connections Per Route to be more realistic and since 
HttpClient is now shared between Main Browser thread and the child threads used 
to download resources

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to