Skip to content

Commit

Permalink
add FAQ section [skip ci] (#27)
Browse files Browse the repository at this point in the history
* add FAQ section [skip ci]

* faq update [skip ci]

* Add files via upload

* update [skip ci]

* doc [skip ci]

* doc [skip ci]

* add concurrency [skip ci]

* update [skip ci]

* add docker vs jar charts [skip ci]

* [skip ci]

* add docker vs jar charts [skip ci]

* add docker vs jar charts [skip ci]
  • Loading branch information
veronikaKochugova authored Feb 20, 2020
1 parent 9f1b147 commit 6b4a05c
Show file tree
Hide file tree
Showing 5 changed files with 48 additions and 0 deletions.
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@
6. [Documentation](doc) 📄 <br/>
7. [Contributing](doc/contributing)<br/>
8. [Changelog](doc/changelog)<br/>
9. [FAQ](doc/faq) ❓ <br/>

# 1. Overview

Expand Down
47 changes: 47 additions & 0 deletions doc/faq/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
# FAQ

## What is *latency* and *duration*?

![](mongoose-lat-dur.png)

A = mongoose start formulate a request

B = mongoose sent the first byte to storage

C = mongoose get the first byte of response from storage

D = mongoose get the last byte of response from storage; operation finish

**Latency = C-B** : this value is measured in nanoseconds and shows how much time passed since mongoose sent first byte to storage till first byte from storage was returned. This value depends on object size in case of Create or Update, and doesn't in case of Read and Delete.

**Duration = D-A** : total operation time (this value is measured in nanoseconds).

## What is *concurrency*?

**Concurrency level** = count of concurrently executed load operations/ the number of open connections at any moment of time ( in terms of the [netty driver](https://github.com/emc-mongoose/mongoose-storage-driver-netty) and its ["child" drivers](https://github.com/emc-mongoose/mongoose#dependency)).

## How to deploy with docker or jar?

We recommend deploying the mongoose with **docker**, because:

* no need to have specific version of java on your machine;
* no need to search for the latest jar file and download it from maven;
* no need to search and download jar with extensions for each storage driver;
* and all the other [advantages of docker](https://dzone.com/articles/top-10-benefits-of-using-docker)

## Does docker affect tool performance?

3 tests were performed for each item-size (10B-100MB):
* mongoose-storage-driver-s3 + minio server
* standalone mode
* CREATE operations

AVG Bandwith:

![](../images/docker_vs_jar_bw.png)

AVG Latency:

![](../images/docker_vs_jar_lat.png)


Binary file added doc/faq/mongoose-lat-dur.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added doc/images/docker_vs_jar_bw.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added doc/images/docker_vs_jar_lat.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 6b4a05c

Please sign in to comment.