v3.3 Overview

Location

https://github.com/emc-mongoose/mongoose/releases/download/3.3.0/mongoose-3.3.0.tgz

Release Notes

New Features and Enhancements

Functional

1. Multiuser Load Case

   Sometimes the performance depends on how many distinct users are using a storage concurrently. This may happen because each user may allocate some transient resources on the storage side. The feature is designed to test the performance in the multi-user environment.

Fixed Bugs

TODO

Miscellaneous

1. Modularity

   1. Custom Storage Driver Plugin

      Initially Mongoose worked via Amazon S3 REST API. Then support for the EMC Atmos and OpenStack Swift API had been added. Finally Mongoose was redesigned to support the work with filesystem what made Mongoose load engine independent on the particular storage type. Currently adding the support of any other storage type supporting CRUD operations is not a trouble.

      It's time to enhance the range of the storage types supported by Mongoose. The way to do this is described in the documentation.

   2. The storage mock aka "Nagaina" moved to the separate project

      That was done to make Mongoose even more modular and even lighter in size. Nagaina has its own docker image and released tarballs.

   3. Mongoose Components are available in the Maven Central Repo.

      This will allow to use to embed any Mongoose functionality into an user application.

2. Configuration layout change

   Detailed configuration layout change info:

   Old parameter name (v < 3.3.0)	New parameter name (v >= 3.3.0)
   load-concurrency	storage-driver-concurrency
   load-job-name	test-step-name
   load-limit-count	test-step-limit-count
   load-limit-rate	test-step-limit-rate
   load-limit-size	test-step-limit-size
   load-limit-time	test-step-limit-time
   load-metrics-period	test-step-metrics-period
   load-metrics-precondition	test-step-precondition
   load-metrics-threshold	test-step-metrics-threshold
   scenario-file	test-scenario-file
   storage-type*	storage-driver-type*
   storage-http-api*	storage-driver-type*

   (*) Note the last 2 parameters. Saying strictly they are completely deprecated and may not be mapped to the new storage-driver-type parameter safely. But the only case which may cause a failure is setting the deprecated parameter storage-type to the "http" value. This is not expected because in all previous versions storage-type was set to "http" by default.

Documentation

• Quickstart
• User Guide
• Troubleshooting
• Reference
  • Configuration
  • Output
  • Custom Storage Driver Plugin
  • Dependencies
• Design
  • Architecture
  • CLI
  • Components
  • Copy Mode
  • Multipart Upload
  • Byte Ranges Read and Update
  • Chain Operations
  • Intermediate Statistics
  • Mixed and Weighted Load
  • Multiuser Load Case