[
https://issues.apache.org/jira/browse/SOLR-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151602#comment-16151602
]
Michael Braun commented on SOLR-11314:
--------------------------------------
Before change: 1194ms with test class. After: 815ms.
After this and change from SOLR-11242 applied, the time goes down further to
659ms.
> 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
> Attachments: 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]
