Differences

This shows you the differences between two versions of the page.

--- test_table [2016/12/07 20:02]
mgstauff
+++ test_table [2016/12/14 16:21] (current)
mgstauff
@@ Line 1: / Line 1: @@
-**Cluster CPU/Memory Usage Report**
+**Cluster Slot Usage (CPU & Memory) Report**
 This table shows cluster cpu/memory usage for ''qsub'' jobs in terms of "Slot Equivalent Time" by periods of 'day' and 'division'. ''qlogin'' jobs/sessions are not reported.
-The goal of this report is to help with deciding what how many slots per "High-speed Slot Group" to request for your group. For a discussion on slots and Slot Groups, [[cluster_billing#slot_groups|click here]].
+The goal of this report is to help with deciding what how many slots per "High-speed Project Slot Quota" to request for your group. For a discussion on slots and Project Slot Quotas, [[cluster_billing#slot_groups|click here]]. Note that slots are added to Project Slot Quotas in increments of 16, so there is a 16-slot minimum for a High-speed Project Slot Quota.
-__NOTE__ Slot Group quotas have not yet been implemented on the cluster, but will be very soon. Once this is done, each job will be assigned to an SGE project (with the same name as a slot group) to track and limit by Slot Group quotas. For users who work with multiple groups or labs, this means their quotas will then be set based on the project they assign to their jobs, allowing them to work flexibly with multiple labs. However, the report below is from jobs that do not include that information, so users who work within multiple groups have their usage below reported only as a part of their 'home' group/lab.
+__NOTE__ Project Slot Quotas will be put into use very soon. Once this is done, each job will be assigned to an SGE project (with the same name as a Project Slot Quota) to track and limit resources by Project Slot Quota. For users who work with multiple groups or labs, this means their quotas will then be set based on the project they assign to their jobs, allowing them to work flexibly with multiple labs. However, the report below is from jobs that do not include that information, so users who work within multiple groups have their usage below reported only as a part of their 'home' group/lab.
 **TERMINOLOGY**
@@ Line 44: / Line 44: @@
 The most important values are the first three columns: '# of non-zero days', and the average and standard deviation values reported under 'SET By Day'.
-Check how many days your group had jobs running, and then the SET values. For example if your number of non-zero days is high compared to the number of days in the report, you may want to simply add the average "SET by Day" to its standard deviation to allow users to generally run the same number of jobs as they have in the past. If your number of non-zero days is low, consider just the "SET by Day" average to save on Slot Group fees.
+Check how many days your group had jobs running, and then the SET values. For example if your number of non-zero days is high compared to the number of days in the report, you may want to simply add the average "SET by Day" to its standard deviation to allow users to generally run the same number of jobs as they have in the past. If your number of non-zero days is low, consider just the "SET by Day" average to save on Project Slot Quota fees.
 You can also consider the "SET By Div" data. If these values are significantly higher, it probably indicates users are running (possibly shorter jobs) during the same time periods, e.g. during the work day. In that case you may want to use these numbers to decide how many slots to request.

Computing

User Tools

Site Tools

Differences

Page Tools