[
https://issues.apache.org/jira/browse/IMPALA-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796500#comment-16796500
]
ASF subversion and git services commented on IMPALA-5393:
---------------------------------------------------------
Commit d3428a58d8f54d1a64d5aeb1af3f76b7ffcb53d0 in impala's branch
refs/heads/master from Lars Volker
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=d3428a5 ]
Revert "IMPALA-5393. Use THREAD_LOCAL state for regexp"
This depends on a change which switches to a toolchain version that does not
have packages for Ubuntu 18.04. Reverting both now to unblock everyone.
This reverts commit 6e8c330f40da087ca0d8ba844cd9d97a8e60ff67.
Change-Id: Id35a90a58e3f775031a0f147b042ccd46d77e24b
Reviewed-on: http://gerrit.cloudera.org:8080/12791
Reviewed-by: Lars Volker <[email protected]>
Tested-by: Lars Volker <[email protected]>
> Regexp should use THREAD_LOCAL context rather than FRAGMENT_LOCAL
> -----------------------------------------------------------------
>
> Key: IMPALA-5393
> URL: https://issues.apache.org/jira/browse/IMPALA-5393
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.8.0
> Reporter: Doug Cameron
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: Impala 3.3.0
>
>
> The RE2 library uses mutex locking around some internal state structures.
> This causes severe lock contention and lack of CPU scaling on the regexp
> string function.
> Switching to THREAD_LOCAL context will remove the contention.
> We could add a query option to select between FRAGMENT_LOCAL vs THREAD_LOCAL
> but that seems overkill as the context is not huge.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
