You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User Story: As a SIMS team, we need to optimize resources effectively as there are only a limited number of shared computing resources across the many government teams.
Acceptance Criteria:
This effort is targeting CPU resource adjustment ONLY and exposing memory configuration also (NO MEMORY CHANGES REQUIRED AT THIS POINT).
For CPU optimization for DEV/TEST, collect current values and suggest some new values to be shared with the Team.
For other environments but DEV/TEST, have the variables configured with the current values.
For resources with individual configuration files: Redis, Crunchy, and ClamAV.
Reduce CPU utilization for DEV and TEST config files.
For resources without individual configuration files (api, queue-consumers, workers, web, form.io, mongo DB)
Expose per environment configuration for all PODs for CPU/memory as GitHub env variables. The deployments (yml) files should have parameters for CPU_LIMIT/CPU_REQUEST and MEMORY_LIMIT/MEMORY_REQUEST.
Remove CPU limits configuration from the yml deployments following the General guidelines from BC Gov.
Create new GitHub env variables for each deployment config to allow per environment configuration for each one.
For instance, for queue-consumers, create the below.
QUEUE_CONSUMERS_CPU_REQUEST
QUEUE_CONSUMERS_MEMORY_REQUEST (use the same value for MEMORY_LIMIT/MEMORY_REQUEST).
Have the variables mapped in the make file with the current default values hard-coded in the yml file as default values in the make variable declaration.
The text was updated successfully, but these errors were encountered:
User Story: As a SIMS team, we need to optimize resources effectively as there are only a limited number of shared computing resources across the many government teams.
Acceptance Criteria:
Redis
,Crunchy
, andClamAV
.CPU_LIMIT/CPU_REQUEST
andMEMORY_LIMIT/MEMORY_REQUEST
.The text was updated successfully, but these errors were encountered: