-
Notifications
You must be signed in to change notification settings - Fork 107
Add blazemeter taurus bench-script #148
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
Conversation
|
Thanks Ricardo, here are my notes from looking it over:
|
|
@rflorenc, thanks this is a great start. We can work through the pip -> rpm dependencies. |
|
Really glad to see a new benchmark script here. I think this is a good time to create a checklist for benchmarks. We can maintain this list in the top of the benchmark script, so users know what common pbench features are present in that script. For example: [y/n] package dependency/installation management others? Good examples of the first 5 features are in pbench_uperf |
The travis build environment (ubuntu precise) supports python3.2 only. Recent pip apparently has *stopped* supporting python3.2. We had to go through hoops to make the previous environment work, but that is now broken. So we go through a different set of hoops that make the build work, but there now seem to be unit test failures that were not there before: they are under investigation.
|
Thank you all for the feedback!
|
The indexing tests are failing in the new travis-ci environment: the pretty-printing is done slightly differently locally, causing spurious failures. I'll revisit them after the 0.36 pbench-agent release (which does not depend on these tests at all).
Fix travis build.
Added a description in the beginning of the file similar to the one found in the other bench tools.
|
I totally agree that we should be consistent with the way the rest of the bench scripts are solving their dependencies through rpm, but in this case since it's a python wrapper for an external tool (also python) you would potentially avoid problems in the future. This is where bzt takes its dependencies from: Pip takes care of updating/upgrading the app as needed from the python package index. |
It only output the first one, but it is called with "$@", which expands to multiple arguments. Opportunistically, delete duplicate run of util-scripts unittests from .travis.yml.
Make debug_log deal with all its arguments.
…yeder/pbench into jeremyeder-fix_openvswitch_dump_ports
Try first without a protocol argument, but if that fails, try with OpenFlow13.
…orts Jeremyeder fix openvswitch dump ports
This convention was used in the util scripts renaming, and will be the established convention henceforth.
Clarified message logged for ssh connection error
Rename benchmark scripts from pbench_foo to pbench-foo.
All the util scripts now have a prefix of pbench-. Move non-pbench scripts to contrib/ subdirectory. contrib/ is not added to the PATH so there will be no collision. If users want to use one or more of these, they will need to call them by full pathname or add contrib/ to their PATH. Add a backward-compatibility wrapper temporarily. We maintain compatibility with the old util-scripts names *for one release only*. The old names will be symlinked to this wrapper in a postinstall action when the RPM is installed. The wrapper does some minimal checking, issues a big fat warning and then executes the script under its new name.
Rename util scripts to avoid collisions.
…scenario files. Added initial platform detection code.
|
@jeremyeder , @portante |
|
@rflorenc ok -- I read the readme. The content is good, I just wonder if it's obvious enough being inside the pbench_bzt file. Maybe we need man pages, or to put README_pbench_bzt.md in the higher-level "doc" folder in pbench? I think there is markdown2man converter somewhere that could make this very easy. Anyway... @atheurer has laid out a list of requirements, where does pbench_bzt stand on these 6 items? |
|
We could have several README_pbench_$tool.md under pbench/agent/bench-scripts/doc with the initial description every bench script has. And maybe later turn those into man pages. The scripts would just contain the checklist @atheurer suggested, in the beginning. |
Rename user-benchmark to pbench-user-benchmark.
reduce sampling interval for perf to 100Hz
Its functions have been taken over by pbench-clear-tools: pbench-clear-tools --group=foo --name=bar will delete the "bar" tool from the "foo" tool group. With no options, it will clear all tools from all groups. With only a --name option, it will delete the named tool from the default group *only*. Fix typo in pbench-bc-wrapper.
Delete obsolete pbench-unregister-tools.
fix syntax to freq argument
Version bump.
|
Can you rebase on latest master and rename it to pbench-bzt? |
Added a description in the beginning of the file similar to the one found in the other bench tools.
…scenario files. Added initial platform detection code.
|
@ndokos , done. |
|
Thanks! |
|
I think the plan for moving ahead with this is:
Agreed? |
|
Yes, thanks. Meanwhile I'll look further into the missing bits. |
This adds support for executing blazemeter taurus (bzt) performance tests.
The main dependency is bzt, which can be installed using the pip package management system for python.
http://gettaurus.org/docs/Installation/#CentOS