-
Notifications
You must be signed in to change notification settings - Fork 36
Performance testing #990
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
base: main
Are you sure you want to change the base?
Performance testing #990
Changes from 12 commits
02c4b94
36ee676
c5c91ac
28aeaa8
7d357f3
f754edf
90c762a
3838013
e38f0d9
df8eaf9
6a61a7a
c7e8270
6ff135f
93de0ea
ab5ece2
f62ca9a
d7c14bf
4d0b746
94fca10
3e57537
8da8c6b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -73,6 +73,24 @@ From the root of the project run the following command (this will run both the u | |
|
|
||
| `python -m pytest tests` | ||
|
|
||
| ### **Performance Testing** | ||
|
|
||
| This repository includes a performance testing script located in the `tests` folder under the filename `PerformanceTest.py`. The script is designed to evaluate the execution time of rules against datasets by running multiple test iterations. | ||
|
|
||
| ### Running the Performance Test | ||
|
|
||
| To execute the performance test, navigate to the root directory of the project and run the following command: | ||
|
|
||
| ```sh | ||
| python tests/PerformanceTest.py -dd <DATASET_DIRECTORY> -rd <RULES_DIRECTORY> -total_calls <NUMBER_OF_CALLS> -od <OUTPUT_DIRECTORY> | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If this is the same as the |
||
| ``` | ||
| ### Performance Test Command-Line Flags | ||
|
|
||
| - **`-dd` (Dataset Directory)**: The directory containing the dataset files in `.json` or `.xpt` format. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Format the documentation similar to the existing documentation. For example, use a code block for the args |
||
| - **`-rd` (Rules Directory)**: The directory containing rule files. | ||
| - **`-total_calls` (Total Calls)**: The number of times each rule should be executed for performance analysis. | ||
| - **`-od` (Output Directory, Optional)**: The directory where the output report (`rule_execution_report.xlsx`) will be saved. By default, the report is saved in the current working directory. | ||
|
|
||
| ### **Running a validation** | ||
|
|
||
| #### From the command line | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and the next header should be nested under the Performance Testing header. IOW, use 4
#