GitHub user srouthiau opened a pull request:

    https://github.com/apache/httpcore/pull/9

    Reuse of SessionInputBuffer and SessionOutputBuffer internal buffers

    Commit 
https://github.com/apache/httpcore/commit/47654da6f027af3cbbd27600ba6df0911e529387
    
    Reusing of internal buffer to limit memory usage. Performance improvements 
on our load tests.

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

    $ git pull https://github.com/srouthiau/httpcore trunk

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

    https://github.com/apache/httpcore/pull/9.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 #9
    
----
commit b998fe991e97e1ccef208350dbbca6c2a751359c
Author: srouthiau <[email protected]>
Date:   2014-09-10T15:24:19Z

    Update AbstractNIOConnPool.java

commit 81c740937be7fb95cc42b195c15c6a185d5937ec
Author: srouthiau <[email protected]>
Date:   2014-09-10T15:25:00Z

    Update RouteSpecificPool.java

commit dc8ebf14b0b21311ac2005a2e53de155439784a1
Author: srouthiau <[email protected]>
Date:   2014-09-10T15:26:11Z

    Update SessionRequestCallback.java

commit 3895133eb24e585b80a8145c15aeb04e1ba74e07
Author: srouthiau <[email protected]>
Date:   2014-09-10T15:27:04Z

    Update DefaultConnectingIOReactor.java

commit 47654da6f027af3cbbd27600ba6df0911e529387
Author: srouthiau <[email protected]>
Date:   2015-03-19T14:48:25Z

    reuse of SessionInputBuffer and SessionOutputBuffer internal buffers

----


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to