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

5977 memory benchmark test #6187

Merged
merged 12 commits into from
Sep 30, 2019
Merged

5977 memory benchmark test #6187

merged 12 commits into from
Sep 30, 2019

Conversation

landreev
Copy link
Contributor

New Contributors

Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Thanks!

Related Issues

Pull Request Checklist

@dataversebot
Copy link

Can one of the admins verify this patch?

@coveralls
Copy link

coveralls commented Sep 19, 2019

Coverage Status

Coverage decreased (-0.002%) to 19.506% when pulling eeff570 on 5977-memory-benchmark-test into 90346b2 on develop.

@djbrooke
Copy link
Contributor

@landreev, I added this to the project board but kept it in the dev column for now. Feel free to move it over when you're ready for code review.

@djbrooke djbrooke moved this from IQSS Team Dev 💻 to Code Review 🦁 in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34) Sep 19, 2019
@djbrooke djbrooke assigned pdurbin and landreev and unassigned landreev Sep 19, 2019
IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34) automation moved this from Code Review 🦁 to QA Sep 19, 2019
Copy link
Member

@pdurbin pdurbin left a comment

Choose a reason for hiding this comment

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

@landreev I'm approving this pull request (looks good!) but I did add a couple of comments for some small things you could change if you want.

curl -O https://raw.githubusercontent.com/IQSS/dataverse-sample-data/memory-monitoring-experiments/ec2config_memory_test.yaml

# run the script:
./ec2-create-instance.sh -a ec2-memory-benchmark -b ${dataverse_branch} -r https://github.com/IQSS/dataverse.git -g ec2config_memory_test.yaml 2>&1 | tee create-instance.log
Copy link
Member

Choose a reason for hiding this comment

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

Instead of hard coding the IQSS repo here, should we allow any fork to be specified? We could always add this later, of course.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right now it's not going to work with any other branch. On account of the bombing external tools, for example. We'll want to add this later, yes.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, sounds good.


# install gnuplot, quietly:

yum -y install gnuplot >/dev/null
Copy link
Member

Choose a reason for hiding this comment

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

For "yum install" to work, the script has to be run as root, right? Should we do a check for this above? Check to make sure the script is being run as the root user, I mean.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are other things in the script that need root. It is run by the parent script as "sudo ec2-memory-benchmark-remote.sh".
In the current setup, this second (remote) script should never be run by the end user directly.

Copy link
Member

Choose a reason for hiding this comment

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

Ah, I didn't notice the sudo. Thanks.

select pages, then taking snapshots of the allocated classes on the
heap and the garbage collection stats; see the issue for more info).

In the curret implementation we are testing the two most used pages -
Copy link
Member

Choose a reason for hiding this comment

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

Typo: curret

@pdurbin pdurbin removed their assignment Sep 19, 2019
@kcondon kcondon self-assigned this Sep 20, 2019
@kcondon kcondon merged commit ad58d80 into develop Sep 30, 2019
@kcondon kcondon deleted the 5977-memory-benchmark-test branch September 30, 2019 17:15
@pdurbin pdurbin added this to the 4.17 milestone Oct 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Better Detection of Memory Leaks/Usage
6 participants