Bot releases are hidden (Show)
Published by akurilov almost 8 years ago
Published by akurilov almost 8 years ago
Published by akurilov almost 8 years ago
Published by akurilov almost 8 years ago
Published by akurilov about 8 years ago
Published by akurilov about 8 years ago
Published by akurilov about 8 years ago
Published by akurilov about 8 years ago
Published by akurilov about 8 years ago
Published by akurilov about 8 years ago
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
The output includes the following new metrics:
For details refer to http://emc-mongoose.github.io/mongoose/usage-results-analysis.html
Published by akurilov over 8 years ago
Published by akurilov over 8 years ago
Mongoose Web GUI is reworked to work with 2.x versions.
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's required to have an ability to loop over the load jobs list. The loop may be:
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.
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 |