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

[DOCS] Removes transform performance note #55177

Merged
merged 3 commits into from Apr 15, 2020

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Apr 14, 2020

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

Copy link
Contributor

@hendrikmuhs hendrikmuhs left a comment

Choose a reason for hiding this comment

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

LGTM

@hendrikmuhs
Copy link
Contributor

Still LGTM.

FWIW, future outlook: Once #54862 is available (probably 7.8) we can hint towards throttling in order to limit resource usage.

aggregation that it performs and the indexing process.
{transforms-cap} perform search aggregations on the source indices then index
the results into the destination index. Therefore, a {transform} never takes
less time than the cumulated duration of the aggregation and the indexing
Copy link
Contributor

Choose a reason for hiding this comment

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

never takes less time

This is not just about duration but also about memory and CPU. Perhaps this could say that it never takes less time or uses less resources ..

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, thanks!

@lcawl lcawl merged commit 079a14e into elastic:master Apr 15, 2020
@lcawl lcawl deleted the transform-performance branch April 15, 2020 17:40
yyff pushed a commit to yyff/elasticsearch that referenced this pull request Apr 17, 2020
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.

None yet

5 participants