IntenseFinance/nosqlbench
3
0
Fork 0
mirror of https://github.com/nosqlbench/nosqlbench.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity

Buildfixes, trying to unblock current builds (#777)

Browse Source 
* make example/test script more robust for meager github actions environment
* improve wording around op template resolution
* remove blocking issues github actions plugin, since it is broken
This commit is contained in:
Jonathan Shook 2022-11-11 16:17:36 -06:00 committed by GitHub
parent 7c1fb19632
commit 2b9452fde4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 14 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.github/workflows/blocking_issues.yml vendored
View File

@ -1,15 +0,0 @@
name: Blocking Issues
on:
issues:
types: [closed]
pull_request_target:
types: [opened, edited]
jobs:
blocking_issues:
runs-on: ubuntu-latest
name: Checks for blocking issues
steps:
- uses: Levi-Lesches/blocking-issues@v1.1

18
adapters-api/src/main/resources/workload_definition/README.md
View File

@ -63,17 +63,21 @@ The process of loading a workload definition occurs in several discrete steps du
session:
1. The workload file is loaded.
2. Template variables are interposed.
2. Template variables from the activity parameters are interposed into the raw contents of the
file.
3. The file is deserialized from its native form into a raw data structure.
4. The raw data structure is transformed into a normalized data structure according to the Op
Template normalization rules.
5. The data is provided to the ParsedOp API for use by the developer.
6. The DriverAdapter is loaded which understands the op fields provided in the op template.
7. The DriverAdapter uses its documented rules to determine which types of native driver operations
5. Each op template is then denormalized as a self-contained data
structure, containing all the provided bindings, params, and tags from the upper layers of the
doc structure.
6. The data is provided to the ParsedOp API for use by the developer.
7. The DriverAdapter is loaded which understands the op fields provided in the op template.
8. The DriverAdapter uses its documented rules to determine which types of native driver operations
each op template is intended to represent. This is called **Op Mapping**.
8. The DriverAdapter uses the identified types to create dispensers of native driver operations.
This is called **Op Dispensing**.
9. The op dispensers are arranged into an indexed bank of op sources according to the specified
9. The DriverAdapter (via the selected Op Mapper) uses the identified types to create dispensers of
native driver operations. This is called **Op Dispensing**.
10. The op dispensers are arranged into an indexed bank of op sources according to the specified
ratios and or sequencing strategy. From this point on, NoSQLBench has the ability to
construct an operation for any given cycle at high speed.

8
nbr-examples/src/test/resources/scripts/examples/extension_histostatslogger.js
View File

@ -18,16 +18,14 @@ activitydef = {
"alias" : "testhistostatslogger",
"driver" : "diag",
"cycles" : "50000",
"threads" : "20",
"interval" : "2000",
"targetrate" : "10000.0",
"threads" : "5",
"rate" : "100.0",
"op" : "noop"
};
histostatslogger.logHistoStats("testing extention histostatslogger", ".*", "logs/histostats.csv", "0.5s");
print("started logging to logs/histostats.csv for all metrics at 1/2" +
" second intervals.");
scenario.start(activitydef);
scenario.waitMillis(2000);
scenario.waitMillis(4000);
scenario.stop(activitydef);