[BUG] The RS add-on S2-L1 v1.7 (and v1.8) does not reach timeliness performance requested for Production Service operation.

[pcuq-ads]

Environment:

• Platform: OPS Orange Cloud
• Configuration: OPS
• Infrastructure v1.5.0
• RS add-on S2-L1 1.7.0-rc1

Current Behavior:
During the S2-L1 add-on benchmarking, it appears that several execution workers (run in series) exceeds 75 minutes each one for long data strip (> 11 minutes).

Expected Behavior:
For Production Service, each S2-L1 execution shall spend less then 75 minutes (around 60 minutes to let level-0 and compression steps completing the chain on time).

Steps To Reproduce:
Benchmark S2-L1 with a data strip length greater then 11 minutes.

According to the benchmark report for S2-L1 v1.7, we have following figures :

• ew-l1ab: 1,8 hours
• ew-l1sa : 4,3 hours
• ew-l1sb : 5,1 hours

Please note that these values are for the worst case.

Whenever possible, first analysis of the root cause

Bug Generic Definition of Ready (DoR)

• The affect version in which the bug has been found is mentioned
• The context and environment of the bug is detailed
• The description of the bug is clear and unambiguous
• The procedure (steps) to reproduce the bug is clearly detailed
• The tested User Story / features is linked to the bug if available
• Logs are attached if available
• A data set attached if available

Bug Generic Definition of Done (DoD)

• the modification implemented (the solution to fix the bug) is described in the bug.
• Unit tests & Continuous integration performed - Test results available - Structural Test coverage reported by SONAR
• Code committed in GIT with right tag or Analysis/Trade Off documentation up-to-date in reference-system-documentation repository
• Code is compliant with coding rules (SONAR Report as evidence)
• Acceptance criteria of the related User story are checked and Passed