[
https://issues.apache.org/jira/browse/SOLR-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157973#comment-16157973
]
ASF subversion and git services commented on SOLR-11314:
--------------------------------------------------------
Commit 21b48b0538e676a7864c39f0d05fdfb45ffef9a3 in lucene-solr's branch
refs/heads/branch_7x from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=21b48b0 ]
SOLR-11314: FastCharStream: re-use the READ_PAST_EOF exception
(cherry picked from commit 89feb15)
> FastCharStream should avoid creating new IOExceptions as a signaling mechanism
> ------------------------------------------------------------------------------
>
> Key: SOLR-11314
> URL: https://issues.apache.org/jira/browse/SOLR-11314
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.0, 6.6.1, master (8.0)
> Reporter: Michael Braun
> Assignee: David Smiley
> Attachments: Screen Shot 2017-09-06 at 8.21.18 PM.png,
> SOLR-11314.patch, TestQueryPerfSpeedup.java
>
>
> FastCharStream is used internally by solr query parser classes. It throws a
> new IOException to signal the end. However, this is quite expensive relative
> to most operations and it shows up very high on samples for extremely high
> query cases. The IOException should be a single static instance that can be
> shared to avoid the overhead in creation and populating the stack trace, a
> stack trace which is never used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
