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

Report indexing times per shard #514

Merged
merged 1 commit into from
May 30, 2018

Conversation

danielmitterdorfer
Copy link
Member

With this commit we do not only show the total indexing times (across
all shards) but also report the indexing times per (primary) shard.

Closes #374

With this commit we do not only show the total indexing times (across
all shards) but also report the indexing times per (primary) shard.

Closes elastic#374
@danielmitterdorfer danielmitterdorfer added enhancement Improves the status quo :Metrics How metrics are stored, calculated or aggregated :Reporting Command line reporting labels May 30, 2018
@danielmitterdorfer danielmitterdorfer added this to the 1.0.0 milestone May 30, 2018
@danielmitterdorfer danielmitterdorfer removed the :Metrics How metrics are stored, calculated or aggregated label May 30, 2018
Copy link
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

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

LGTM! Left a suggestion to stick to append() instead of += when appending items in lists.

@@ -665,19 +705,38 @@ def report_merge_part_times(self, baseline_stats, contender_stats):
)

def report_total_times(self, baseline_stats, contender_stats):
totals = []
totals += self.report_total_time("indexing time",
Copy link
Contributor

Choose a reason for hiding this comment

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

As discussed, append() could be a better choice as += with lists may produce unexpected results if the input is a string vs a list.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, good suggestion! I'll merge this PR and do this separately.

Copy link
Member Author

Choose a reason for hiding this comment

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

Addressed in 8d7a799.

@danielmitterdorfer danielmitterdorfer merged commit e6e618c into elastic:master May 30, 2018
@danielmitterdorfer danielmitterdorfer deleted the index-metrics branch May 30, 2018 07:43
danielmitterdorfer added a commit that referenced this pull request May 30, 2018
With this commit we use a custom structure in the ES metrics store for
per shard statistics instead of the generic `value.single` one.

Relates #514
danielmitterdorfer added a commit that referenced this pull request May 30, 2018
With this commit we specify that values should be stored as doubles
instead of floats (which are implicitly assumed) in order to ensure that
we can store larger values as well.

Relates #514
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves the status quo :Reporting Command line reporting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants