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

DO NOT MERGE - Pipeline performance test project #4154

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

lrcouto
Copy link
Contributor

@lrcouto lrcouto commented Sep 10, 2024

Description

Kedro project made to simulate delays and latency in specific points of a Kedro pipeline. Pass the desired delays in seconds using the --params flag. For example:

kedro run --params=hook_delay=5,dataset_load_delay=5,file_save_delay=5

Development notes

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

  • Read the contributing guidelines
  • Signed off each commit with a Developer Certificate of Origin (DCO)
  • Opened this PR as a 'Draft Pull Request' if it is work-in-progress
  • Updated the documentation to reflect the code changes
  • Added a description of this change in the RELEASE.md file
  • Added tests to cover my changes
  • Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

Signed-off-by: Laura Couto <[email protected]>
Signed-off-by: Laura Couto <[email protected]>
@lrcouto lrcouto marked this pull request as ready for review September 12, 2024 00:10
Copy link
Contributor

@noklam noklam left a comment

Choose a reason for hiding this comment

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

Thanks! I am not able to run the pipeline with missing data so I just quickly review it on a high level.

Can you add some description do the PR explaining how to use this pipeline test. I see that most of the pipeline here are mocking with sleep, why did you end up going with this implementation?

For example, if I want to answer the question, does Kedro run too slow when it needs to connect to a database, what command should I run?

@@ -0,0 +1,20 @@
# What is this for?

This folder should be used to store configuration files used by Kedro or by separate tools.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any specific configuration needed to be documented? Otherwise I think we can remove this from our project

@@ -0,0 +1,98 @@
# performance-test
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe it's more helpful to document how this project should be used, otherwise I suggest removing it as these template doesn't add much information for us.

Comment on lines 32 to 40
def register_pipelines(self) -> Dict[str, Pipeline]:
from performance_test.pipelines.expense_analysis import (
pipeline as expense_analysis_pipeline,
)

return {
"__default__": expense_analysis_pipeline.create_pipeline(),
"expense_analysis": expense_analysis_pipeline.create_pipeline(),
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this belongs to pipeline_registry.py?

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

Successfully merging this pull request may close these issues.

[Stress Testing] - Create example projects to assess Kedro performance for complex pipelines
2 participants