Testing/test arched reliability EMI1 RC3

P1: service reliability

• Tester: Gabor
• due: 25 March

Services run by the component must maintain a good performance and reliability over long periods of time with normal operation. Long running unattended operation test measuring performance of the product. Service must not show performance degradation during a 3-day period.

• Description of the test:

First time see the times to return 100 arcecho requests (simultaneous and sequential). Then repeat a following cycle for three days - every 5 minutes use the perftest utility with input parameters 50 threads, 30 seconds. After every day try to measure the times to return 100 arcecho requests (simultaneous and sequential) and make some conclusion when comparing the times to times from beginning of test.

Package: EMI1-RC[1,3]

• at the beginning
  • arcecho request time

RC1	RC3
Sequential: real 0m10.240s user 0m0.935s sys 0m0.431s Simultaneous: real 0m1.663s user 0m0.867s sys 0m0.423s	Sequential: real 0m10.493s user 0m1.341s sys 0m0.547s Simultaneous: real 0m2.203s user 0m1.1247s sys 0m0.514s

• • Memory usage: (after the hed start [idle hed] and before the arcechos requests)

RC1	RC3
%CPU %MEM VSZ RSS 0.3 0.6 202864 6436	not idle HED %CPU %MEM VSZ RSS 1.1 1.3 309608 13612

• after one day
  • arcecho request time

RC1	RC3
Sequential: real 0m10.275s user 0m0.985s sys 0m0.505s Simultaneous: real 0m1.912s user 0m0.900s sys 0m0.504s	Sequential: real 0m10.393s user 0m1.251s sys 0m0.577s Simultaneous: real 0m2.255s user 0m1.237s sys 0m0.549s

• • Memory usage:

RC1	RC3
%CPU %MEM VSZ RSS 2.9 4.8 471312 49848	%CPU %MEM VSZ RSS 3.3 4.6 472736 47468

• after two days
  • arcecho request time

RC1	RC3
Sequential: real 0m10.331s user 0m1.030s sys 0m0.469s Simultaneous: real 0m1.914s user 0m0.975s sys 0m0.503s	Sequential: real 0m10.686s user 0m1.317s sys 0m0.540s Simultaneous: real 0m2.231s user 0m1.213s sys 0m0.501s

• • Memory usage:

RC1	RC3
%CPU %MEM VSZ RSS 2.9 5.0 472428 51932	%CPU %MEM VSZ RSS 3.5 5.6 548272 58224 Temporary value: %CPU %MEM VSZ RSS 3.5 6.2 1339760 63756

• at the end
  • arcecho request time

RC1	RC3
Sequential: real 0m10.276s user 0m1.034s sys 0m0.503s Simultaneous: real 0m1.920s user 0m0.964s sys 0m0.527s	Sequential: real 0m10.464s user 0m1.304s sys 0m0.536s Simultaneous: real 0m2.248s user 0m1.168s sys 0m0.566s

• • Memory usage:

RC1	RC3
%CPU %MEM VSZ RSS 2.5 5.0 472284 52104	%CPU %MEM VSZ RSS 2.2 5.7 548272 58744

• Results
  • CPU usage: PASSED
  • Memory usage: PASSED
  • Request time (sequential): PASSED
  • Request time (simultaneous): PASSED

• conclusions
  • by VERBOSE log level: disk space need for a log around 100MB/ 15 minutes
  • big memory usage peak: 1339760 MB
  • response time change: not relevant difference
    • Sequential:

RC1	RC3
real 0m10.240s -> 10.276s user 0m0.935s -> 1.034s sys 0m0.431s -> 0.503s	real 0m10.493s -> 10.464s user 0m1.341s -> 1.304s sys 0m0.547s -> 0.536s

• • • Simultaneous:

RC1	RC3
real 0m1.663s -> 1.920s user 0m0.867s -> 0.964s sys 0m0.423s -> 0.527s	real 0m2.203s -> 2.248s user 0m1.247s -> 1.168s sys 0m0.514s -> 0.566s

• • memory usage and changes:
    • Virtual memory (KB):

RC1	RC3
202864 -> 472284 = +269420 KB -> 1 day: +268448 KB 1 -> 2 day: +1116 KB 2 -> 3 day: -144 KB	309608 -> 548272 = +238664 KB -> 1 day: +163128 KB 1 -> 2 day: +75536 KB 2 -> 3 day: +-0 KB

• • • non-swapped physical memory (KB):

RC1	RC3
6436 -> 52104 = +45668 KB -> 1 day: +43412 KB 1 -> 2 day: +2084 KB 2 -> 3 day: +172 KB	13612 -> 58744 = +45132 KB -> 1 day: +33856 KB 1 -> 2 day: +10756 KB 2 -> 3 day: +520 KB