Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Wed, 21 Jun 2017 07:45:00 +0000 (UTC)
From: "Arya Ketan (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.13081299.1498012817000.67012.1498031100167@Atlassian.JIRA>
In-Reply-To: <JIRA.13081299.1498012817000@Atlassian.JIRA>
References: <JIRA.13081299.1498012817000@Atlassian.JIRA> <JIRA.13081299.1498012817718@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HTTPCLIENT-1858) Very high GC pressure due to
 wire logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 21 Jun 2017 07:49:44 -0000


     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arya Ketan updated HTTPCLIENT-1858:
-----------------------------------
    Attachment: Screen Shot 2017-06-21 at 1.11.46 pm.png

> Very high GC pressure due to wire logging
> -----------------------------------------
>
>                 Key: HTTPCLIENT-1858
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1858
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.2
>            Reporter: Arya Ketan
>            Priority: Minor
>              Labels: performance
>         Attachments: Screen Shot 2017-06-21 at 1.11.46 pm.png
>
>
> While running performance tests, I am seeing very high GC pressure due to the following code
> in Wire.java 
> {code:java}
> private void wire(final String header, final InputStream instream)
>       throws IOException {
>         final StringBuilder buffer = new StringBuilder();
>         int ch;
>         while ((ch = instream.read()) != -1) {
>             if (ch == 13) {
>                 buffer.append("[\\r]");
>             } else if (ch == 10) {
>                     buffer.append("[\\n]\"");
>                     buffer.insert(0, "\"");
>                     buffer.insert(0, header);
>                     log.debug(id + " " + buffer.toString());
>                     buffer.setLength(0);
>             } else if ((ch < 32) || (ch > 127)) {
>                 buffer.append("[0x");
>                 buffer.append(Integer.toHexString(ch));
>                 buffer.append("]");
>             } else {
>                 buffer.append((char) ch);
>             }
>         }
>         if (buffer.length() > 0) {
>             buffer.append('\"');
>             buffer.insert(0, '\"');
>             buffer.insert(0, header);
>             log.debug(id + " " + buffer.toString());
>         }
>     }
> {code}
> This is because, we are trying to expand Stringbuffer continously , thus leading to lot of char[] garbage. 
> 2 suggestions for improvements
> a) we look into whether logging level is enabled and only then construct the message
> b) efficiently construct log message.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org