Skip to content

Speed up replaceRegexp(All|One) if the pattern is trivial#66185

Merged
rschu1ze merged 2 commits intoClickHouse:masterfrom
rschu1ze:faster_regexp
Jul 8, 2024
Merged

Speed up replaceRegexp(All|One) if the pattern is trivial#66185
rschu1ze merged 2 commits intoClickHouse:masterfrom
rschu1ze:faster_regexp

Conversation

@rschu1ze
Copy link
Copy Markdown
Member

@rschu1ze rschu1ze commented Jul 7, 2024

The idea is to transform replaceRegexp(One|All) into replace(One|All) if the pattern is trivial.

This PR is a continuation of #62436 but compared to the original implementation, ReplaceRegexpImpl keeps using re2 instead of OptimizedRegularExpression to keep the code overall simple and maintainable.

Measurements with haystack Many years later as he faced the firing squad, Colonel Aureliano Buendia was to remember that distant afternoon when his father took him to discover ice. on 5 mio rows

  • and complex pattern \s+ and replacement \\0\n

    • replaceRegexpAll: 13.67 sec
    • replaceRegexpOne: 0.628 sec
  • and trivial pattern (space) and replacement \n:

    • replaceRegexpAll: 1.63 sec
    • replaceRegexpOne: 0.16 sec

Courtesy to @taiyang-li !

Changelog category (leave one):

  • Performance Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Functions replaceRegexpAll and replaceRegexpOne are now significantly faster if the pattern is trivial, i.e. contains no metacharacters, pattern classes, flags, grouping characters etc. (Thanks to Taiyang Li)

@rschu1ze rschu1ze changed the title Speed up replaceRegexp(All|One) if the pattern is trivial Speed up replaceRegexp(All|One) if the pattern is trivial Jul 7, 2024
@robot-ch-test-poll4 robot-ch-test-poll4 added the pr-performance Pull request with some performance improvements label Jul 7, 2024
@robot-ch-test-poll1
Copy link
Copy Markdown
Contributor

robot-ch-test-poll1 commented Jul 7, 2024

This is an automated comment for commit 948565f with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Check nameDescriptionStatus
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests❌ failure
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc❌ failure
Successful checks
Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help✅ success
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
ClickBenchRuns [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docs checkBuilds and tests the documentation✅ success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc✅ success
Install packagesChecks that the built packages are installable in a clear environment✅ success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests✅ success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success
Style checkRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts✅ success

@divanik divanik self-assigned this Jul 8, 2024
Copy link
Copy Markdown
Member

@divanik divanik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

static void vectorFixedConstantConstant(...) - I wonder if we can apply the same optimisation here?

@rschu1ze

This comment was marked as resolved.

@rschu1ze

This comment was marked as resolved.

@rschu1ze rschu1ze added this pull request to the merge queue Jul 8, 2024
@rschu1ze
Copy link
Copy Markdown
Member Author

rschu1ze commented Jul 8, 2024

Perf test failure is because test replaceRegexpFallback only been introduced with this PR.

Merged via the queue into ClickHouse:master with commit 429eed3 Jul 8, 2024
@rschu1ze rschu1ze deleted the faster_regexp branch July 8, 2024 21:49
@robot-clickhouse-ci-1 robot-clickhouse-ci-1 added the pr-synced-to-cloud The PR is synced to the cloud repo label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-performance Pull request with some performance improvements pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants