Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add time measuring metrics for file ingestion in PerfContext #13219

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jowlyzhang
Copy link
Contributor

As titled. And also added some documentation for an approach to name perf context metrics that can help identify the starting PerfLevel that enables collecting it.

Test Plan
Unit test

@facebook-github-bot
Copy link
Contributor

@jowlyzhang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@jowlyzhang jowlyzhang requested a review from anand1976 December 17, 2024 23:00
// These metrics usually have this pattern: "_[wait|delay]_*_[time|nanos]".
kEnableWait = 3,
// Starts enabling metrics that measure the end to end time of an operation.
// These metrics' names have keywords "time" or "nanos". Check other time
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: "time" or time unit e.g, nanos, micros.

opts.allow_blocking_flush = true;
ASSERT_OK(db_->IngestExternalFile({file1}, opts));
ASSERT_EQ(perf_context.file_ingestion_nanos, 0);
ASSERT_EQ(perf_context.file_ingestion_blocking_live_writes_nanos, 0);
Copy link
Contributor

Choose a reason for hiding this comment

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

I assumed your test ensure blocking live writes will happen so this proves your point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants