Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: TAG 2017/18 Sprint 1
-
Component/s: Evaluation Engine / Workers
-
Labels:None
Description
Part of SIO-1928.
Right now, the worker config defines WORKER_CONCURRENCY parameter which is calculated from both CPU number and (RAM / average RAM for a job). This parameter should be split into WORKER_CONCURRENCY that only depends on CPU count, and WORKER_RAM that declares the amount of RAM that can be used.
The default value should leave some RAM for OS usage.
Right now, the worker config defines WORKER_CONCURRENCY parameter which is calculated from both CPU number and (RAM / average RAM for a job). This parameter should be split into WORKER_CONCURRENCY that only depends on CPU count, and WORKER_RAM that declares the amount of RAM that can be used.
The default value should leave some RAM for OS usage.
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
