Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It is approximately the same stable as Nolana.

  • For 1 concurrent job, 100 records can be edited in 1 min 9 s which is 19 s slower compared to Nolana (50 s), and 1000 records editing could be performed in 2 min 54 s  which is 40 s slower compared to Nolana(2 min 10 s), and 10k records bulk editing is about 36% slower.
  • 10k records per user, 5 users simultaneously (50k records total) can be uploaded and edited in about 22 minutes which is about 9 min 30 s slower compared to Nolana (about 12 min 25 s).
  • The memory utilization of mod-bulk operation increases from 20% 23% to 23% 25% (The service was updated before the test, probably it is reaching a steady state- the memory trend will be investigated in further testing). mod-users memory utilization increases from 45 to 47% during the first test with 10k users and was stable for all other tests. For all other modules, no memory leaks are suspected.
  • CPU for all modules did not exceed 56% 79% for all of the tests except the first test for bulk editing with 10k users: mod-users CPU utilization was 157%(at the same time memory grows by 2%) but for all further tests, it was below 80%.
  • For all records number (100, 1k,10k), and 5 concurrent jobs tests - RDS CPU utilization did not exceed 41%59% (for tests with 10k users records). For the tests with 2500 user records did not exceed 27%.


Recommendations & Jiras


Results

...

Job #Job descriptionOrchid DurationBaseline job time
1
10k item records
17 min 48 s17 min 50 s
2
10k holding records
18 min 56 s19 min 33 s
3
10k user records
11 min 45 s11 min 17 s

Memory usage

The memory utilization of mod-bulk operation increases from 23% to 25% (the memory trend will be investigated in further testing).

mod-users memory utilization increases from 45 to 47% during the first test with 10k users and was stable for all other tests.

For all other modules, no memory leaks are suspected.

Instance CPU utilization

Instances CPU utilization did not exceed 16%


Service CPU utilization

CPU for all modules did not exceed 79% for all of the tests except the first test for bulk editing with 10k users: mod-users CPU utilization was 157%(at the same time memory grows by 2%) but for all further tests, it was below 80%.


RDS CPU utilization

For all tests - RDS CPU utilization did not exceed 59% (for tests with 10k users records). For the tests with 2500 user records did not exceed 27%.

Appendix

Infrastructure

PTF -environment ncp5 [ environment name] 

...