Skip to content

Releases: emc-mongoose/mongoose

2.4.0

26 Jul 07:34
Compare
Choose a tag to compare

New Features and Enhanchements

Core Functionality

1. Scenario values substitution with the environment variables

It's possible to substitute a json values in the scenario with the environment variable values. This may help to keep the scenario file unchanged parameterizing the behavior from the command line only.

For details refer to http://emc-mongoose.github.io/mongoose/design-scenario.html#env

2. Metrics output layout major change

The output includes the following new metrics:

  1. Load job elapsed time.
  2. The sum of all I/O task durations for the given load job.
  3. The total byte count been transferred for the given load job.

For details refer to http://emc-mongoose.github.io/mongoose/usage-results-analysis.html

Fixed Bugs

  • Broken custom HTTP headers feature

2.3.2

15 Jul 08:46
Compare
Choose a tag to compare
2.3.2 Pre-release
Pre-release

2.3.0

11 Jul 07:32
Compare
Choose a tag to compare

New Features and Enhancements

Core Functionality

1. Web GUI

Mongoose Web GUI is reworked to work with 2.x versions.

2. Intermediate Statistics

When Mongoose load job starts there's some short delay before the warmup is done and all threads/connections are busy with load tasks. It's expected that the performance rates are lower during this warmup time range. Moreover, at the load job end some threads/connections may remain busy with the load task while other threads/connections are finished already.

  • It is required to measure the performance rates only while all threads/connections are busy with the load tasks.
  • It is expected that the intermediate statistics (the statistics measured in the "full throttle" time range) will contain the "best" performance results.

3. Scenario Engine: "For" Job Type

It's required to have an ability to loop over the load jobs list. The loop may be:

  1. Infinite
  2. Count-based
  3. Iteration over the list of values to be substituted

4. Different Run Ids for the Load Jobs

It's required to have an ability to specify the logs path for each load job separately. The logs path is determined by run id.

Non-functional

Fixed Bugs

Issue Id Description
SLTM-723 Weighted Load: perf.trace.csv loses the load type info
SLTM-723 No perf.sum.csv file after the test

2.3.1

09 Jul 21:43
Compare
Choose a tag to compare

Fixed Bugs

Issue Id Description
13 v2.3.0 performance degradation comparing to v1.3.2