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

Pivotal ID # 185786866: Simple automated performance test #739

Merged

Conversation

Juan-EBI
Copy link
Contributor

@Juan-EBI Juan-EBI commented Aug 8, 2023

@Juan-EBI Juan-EBI requested a review from jhoanmanuelms August 9, 2023 12:12
line()

line("Files")
subFiles.forEach { line(it.name) }
Copy link
Contributor

Choose a reason for hiding this comment

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

The test looks awesome, I think this is worth measuring. I think it could benefit from adding the files through a file list rather than placing them directly in the submission just to add to the test case the overhead of reading the file list at each stage which is our most common case for big submissions.

Also, I think we could increase the number of files to 1000. It'll add an extra minute but the test will be closer to our actual use case.

WDYT?

Copy link
Contributor Author

@Juan-EBI Juan-EBI Aug 10, 2023

Choose a reason for hiding this comment

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

I think it is not a real performance test but rather a simple exercise to monitor performance in really really ideail conditions, I agree with using file list as this does help to test batch processing but 1000 files will be still an small number of files so I do not see much value there. We may think to use 1.000.000 but again this is not a real performance test so IMO it will not add much information than using 100 and will delay test execution.

Copy link
Contributor Author

@Juan-EBI Juan-EBI Aug 10, 2023

Choose a reason for hiding this comment

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

actually just test it with 1000 and runner JVM dies (and I think updating runner to match production machine and get "real performance" is out of the scope)

WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, maybe the execution is too long. I'd still like to see the files in a file list but I'll leave it to you.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

files are inded in a file list already

Copy link
Contributor

@jhoanmanuelms jhoanmanuelms left a comment

Choose a reason for hiding this comment

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

LGTM

@Juan-EBI Juan-EBI merged commit 74750c8 into master Aug 11, 2023
@jhoanmanuelms jhoanmanuelms deleted the feature/pivotal-185786866-Simple-automated-performance-test branch August 16, 2023 14:14
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.

2 participants