[
https://issues.apache.org/jira/browse/SOLR-16265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752122#comment-17752122
]
ASF subversion and git services commented on SOLR-16265:
--------------------------------------------------------
Commit 9b1aba273407d3b15a4f2a9e8b5a7709f3a5f5d4 in solr's branch
refs/heads/main from Alex Deparvu
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=9b1aba27340 ]
SOLR-16265 reduce memory usage of ContentWriter based requests in
Http2SolrClient (#1789)
SOLR-16265 reduce memory usage of ContentWriter based requests in
Http2SolrClient
> reduce memory usage of ContentWriter based requests in Http2SolrClient
> ----------------------------------------------------------------------
>
> Key: SOLR-16265
> URL: https://issues.apache.org/jira/browse/SOLR-16265
> Project: Solr
> Issue Type: Improvement
> Reporter: Chris M. Hostetter
> Assignee: Alex Deparvu
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> I recently noticed the code below exists in
> {{Http2SolrClient.createRequest}}...
> {code}
> if (contentWriter != null) {
> Request req = httpClient.newRequest(url +
> wparams.toQueryString()).method(method);
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> contentWriter.write(baos);
> // TODO reduce memory usage
> return req.content(
> new BytesContentProvider(contentWriter.getContentType(),
> baos.toByteArray()));
> {code}
> * AFAICT there is no (other) existing jira discussing this TODO
> * This method is called for most "simple" HTTP2 based requests
> ** {{Http2SolrClient}} or {{CloudHttp2SolrClient}} -- but not
> {{ConcurrentUpdateHttp2SolrClient}}
> * This block triggers for anything with a {{ContentWriter}}
> ** ie: all {{UpdateRequests}} ... and in theory other custom requests
> * Part of the issue seems to be that this code repurposes the
> {{ContentWriter}} "push" style API into a "pull" style Jetty client API
> ** Even though {{Http2SolrClient}} has other code used only by
> {{ConcurrentUpdateHttp2SolrClient}} ({{initOutStream(...)}}) which does
> leverage a "push" style Jetty client API: {{OutputStreamContentProvider}}
> * But more silly: we make one (serialized) {{byte[]}} of the data in memory
> inside the {{ByteArrayOutputStream}} then we call {{toByteArray()}} which
> makes a second copy of the {{byte[]}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
