Update s3p Test results

- Update performance test results

Issue-ID: POLICY-3109
Signed-off-by: arkadiusz.adamski <aadamski@est.tech>
Change-Id: Id2deb7f63124e48f1cfcf6c95b47ac71753fbbce

diff --git a/docs/development/devtools/apex-s3p.rst b/docs/development/devtools/apex-s3p.rst
index e3a5d7e..be34f5b 100644 (file)
--- a/docs/development/devtools/apex-s3p.rst
+++ b/docs/development/devtools/apex-s3p.rst
@@ -209,7 +209,7 @@ The Performance test is performed on a similar setup to the Stability test. JMet
 
 Performnce test plan will be the same as the stability test plan except for some differences listed below:
 
-- Increase the number of threads from 5 to 60.
+- Increase the number of threads from 5 to 20.
 - Reduce test time to ninety minutes.
 - Calculate the amount of requests handled in the time frame.
 
@@ -240,11 +240,11 @@ Performance test was triggered for 90 minutes. The results are shown below.
 ============================ =========== ========= ==================================
 **Total Number of Requests** **Success** **Error** **Average Time Taken per Request**
 ============================ =========== ========= ==================================
-9870                         100 %       0 %       5506.09 ms
+32304                        99,99 %     0.01 %    8746.50 ms
 ============================ =========== ========= ==================================
 
 **JMeter Screenshot**
 
-.. image:: images/apex_perf_jm_1.png
+.. image:: images/apex_perf_jm_1.PNG
 
-.. image:: images/apex_perf_jm_2.png
+.. image:: images/apex_perf_jm_2.PNG

diff --git a/docs/development/devtools/images/apex_perf_jm_1.PNG b/docs/development/devtools/images/apex_perf_jm_1.PNG
index 14b1a07..a1852be 100644 (file)
Binary files a/docs/development/devtools/images/apex_perf_jm_1.PNG and b/docs/development/devtools/images/apex_perf_jm_1.PNG differ

diff --git a/docs/development/devtools/images/apex_perf_jm_2.PNG b/docs/development/devtools/images/apex_perf_jm_2.PNG
index 7a2eebb..d91ec4a 100644 (file)
Binary files a/docs/development/devtools/images/apex_perf_jm_2.PNG and b/docs/development/devtools/images/apex_perf_jm_2.PNG differ