Skip to content

New profile events for parallel replicas#69706

Merged
nickitat merged 3 commits intomasterfrom
pror_events_for_pr
Sep 19, 2024
Merged

New profile events for parallel replicas#69706
nickitat merged 3 commits intomasterfrom
pror_events_for_pr

Conversation

@nickitat
Copy link
Member

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-not-for-changelog This PR should not be mentioned in the changelog label Sep 17, 2024
@robot-ch-test-poll3
Copy link
Contributor

robot-ch-test-poll3 commented Sep 17, 2024

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

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

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
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. 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
Stateless testsRuns stateless 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

@kssenii kssenii self-assigned this Sep 18, 2024
M(ParallelReplicasHandleRequestMicroseconds, "Time spent processing requests for marks from replicas") \
M(ParallelReplicasHandleAnnouncementMicroseconds, "Time spent processing replicas announcements") \
M(ParallelReplicasAnnouncementMicroseconds, "Time spent to send an announcement") \
M(ParallelReplicasReadRequestMicroseconds, "Time spent for a read requests") \
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
M(ParallelReplicasReadRequestMicroseconds, "Time spent for a read requests") \
M(ParallelReplicasReadRequestMicroseconds, "Time spent for read requests") \

Comment on lines +47 to +48
size_t number_of_current_replica;
size_t total_nodes_count;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
size_t number_of_current_replica;
size_t total_nodes_count;
const size_t number_of_current_replica;
const size_t total_nodes_count;

auto operator()(Args &&... args)
{
DB::OpenTelemetry::SpanHolder span(span_name);
DB::ProfileEventTimeIncrement<DB::Time::Microseconds> increment(event);
Copy link
Member

Choose a reason for hiding this comment

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

btw we do have two ways to do the same thing: ProfileEventTimeIncrement and ProfileEvent::Timer (looks like auto timer = DB::CurrentThread::getProfileEvents().timer(event);). Should we delete one of them? Just contemplating, not asking you to do anything

Copy link
Member Author

Choose a reason for hiding this comment

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

never saw this one. will try to remove it

@nickitat
Copy link
Member Author

during testing found #69744

@nickitat nickitat added this pull request to the merge queue Sep 19, 2024
Merged via the queue into master with commit 948636c Sep 19, 2024
@nickitat nickitat deleted the pror_events_for_pr branch September 19, 2024 18:19
@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-synced-to-cloud The PR is synced to the cloud repo label Sep 19, 2024
zvonand pushed a commit to Altinity/ClickHouse that referenced this pull request Dec 17, 2024
Enmk pushed a commit to Altinity/ClickHouse that referenced this pull request Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog 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.

4 participants