Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
At the end of August, high CPU usage was detected in a customer project. This lead to some delays to schedule publishing functionality.
To detect this possible delays in scheduled publishing they would like to set up notification at a given threshold.
Facts:
- Checking with Ervin and currently the value can have peaks up to 60% per public
- During the high CPU usage time, this peak raised up to 160% (across 3 publics)
- High peaks on CPU might not lead to delays of scheduled publishing but it could have potential.
If you would see another way to notify possible delays on scheduled publishing, we will welcome the different approach.
Aim: How can we foreseen or mitigate “delays” on schedule publishing
Details of existing investigation in linked tickets:
Checklists
Acceptance criteria