grimboite/articles/dev/2015-12-29-scaleway.rst

147 lines
5.0 KiB
ReStructuredText

Scaleway
========
Utilisation de `Sysbench <https://wiki.gentoo.org/wiki/Sysbench>`_ pour les tests.
Les trois serveurs comparés sont les suivants:
* Un VPS Cloud chez OVH: 4Go de Ram, single-core et SSD de 20Go.
* Un C1 chez Scaleway: 2Go de RAM, quad-core ARMv7 et SSD de 50Go.
* Un Kimsufi KS-1: Atom @ 1.86Ghz (2 coeurs, 4 threads), 2Go de RAM et 500 de disque.
Disk speed
----------
On utilise la commande ``dd`` (http://www.stevefortuna.com/check-disk-speed-quickly-and-easily-in-linux/)
pour simuler une écriture sur disque. Chez OVH, le serveur tourne à **514Mo/s**, tandis qu'il plafonne à **115Mo/s** sur le C1.
Idem pour la vitesse de lecture: chez OVH, on atteint les **2.3Go/s**, tandis que le C1 se voit aux alentours de **130Mo/s**.
Sur le KS-1, on tombe sur les valeurs suivantes: **143Mo/s** en écriture, **145Mo/s** en lecture.
Processeur
----------
On commence par installer ``sysbench`` et on le lance sur les trois machines ``sysbench --test=cpu --cpu-max-prime=20000 run``:
VPS Cloud
.. code-block:: shell
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 29.8127s
total number of events: 10000
total time taken by event execution: 29.8107
per-request statistics:
min: 2.66ms
avg: 2.98ms
max: 6.78ms
approx. 95 percentile: 3.33ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 29.8107/0.00
Sur le C1
.. code-block:: shell
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 686.8824s
total number of events: 10000
total time taken by event execution: 686.8633
per-request statistics:
min: 68.62ms
avg: 68.69ms
max: 76.86ms
approx. 95 percentile: 68.73ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 686.8633/0.00
Sur le KS-1
.. code-block:: shell
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 209.6545s
total number of events: 10000
total time taken by event execution: 209.6493
per-request statistics:
min: 20.94ms
avg: 20.96ms
max: 34.01ms
approx. 95 percentile: 20.98ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 209.6493/0.00
4 Threads
---------
Et la même chose en spécifiant 4 threads (pour profiter des 4 coeurs du processeur ARM): ``sysbench --test=cpu --cpu-max-prime=20000 --num-threads=4 run``.
Sur VPS:
.. code-block:: shell
Test execution summary:
total time: 27.9756s
total number of events: 10000
total time taken by event execution: 111.8676
per-request statistics:
min: 2.50ms
avg: 11.19ms
max: 33.53ms
approx. 95 percentile: 15.28ms
Threads fairness:
events (avg/stddev): 2500.0000/1.22
execution time (avg/stddev): 27.9669/0.01
Et sur le C1:
.. code-block:: shell
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 171.3275s
total number of events: 10000
total time taken by event execution: 685.2335
per-request statistics:
min: 68.46ms
avg: 68.52ms
max: 109.33ms
approx. 95 percentile: 68.54ms
Threads fairness:
events (avg/stddev): 2500.0000/1.22
execution time (avg/stddev): 171.3084/0.01
Sur le KS-1:
.. code-block:: shell
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 86.2656s
total number of events: 10000
total time taken by event execution: 345.0025
per-request statistics:
min: 23.36ms
avg: 34.50ms
max: 78.49ms
approx. 95 percentile: 34.55ms
Threads fairness:
events (avg/stddev): 2500.0000/1.87
execution time (avg/stddev): 86.2506/0.01