Hi, Am 31.07.2015 um 23:00 schrieb Carl G. Riches:
>> <snip> > Thanks for these pointers. After going through these and others, I think I > have a basic understanding of share-tree and functional share policies. I'm > not clear on whether or not these can be combined, but I think so. > > The goal is to limit user access to CPU when there is contention to a queue. > The limit would apply to all users and the limit would be 12% of all CPUs in > a queue. How do you came up with 12% - it will never make exactly 100%? Is the intend to have a fair share scheduling over a time frame then? -- Reuti > There are no "projects" or "departments" at this time. Would these > parameter settings achieve that goal? > > > algorithm default > schedule_interval 0:0:15 > maxujobs 0 > queue_sort_method load > job_load_adjustments np_load_avg=0.50 > load_adjustment_decay_time 0:7:30 > load_formula np_load_avg > schedd_job_info true > flush_submit_sec 0 > flush_finish_sec 0 > params none > reprioritize_interval 0:0:0 > halftime 168 > usage_weight_list cpu=1.000000,mem=0.000000,io=0.000000 > compensation_factor 5.000000 > weight_user 0.640000 > weight_project 0.120000 > weight_department 0.120000 > weight_job 0.120000 > weight_tickets_functional 1000000 > weight_tickets_share 1000 > share_override_tickets TRUE > share_functional_shares TRUE > max_functional_jobs_to_schedule 2000 > report_pjob_tickets TRUE > max_pending_tasks_per_job 50 > halflife_decay_list none > policy_hierarchy OFS > weight_ticket 1000.000000 > weight_waiting_time 0.000000 > weight_deadline 3600000.000000 > weight_urgency 0.100000 > weight_priority 0.100000 > max_reservation 0 > default_duration INFINITY > > > Must we also define a "default" user in some manner such that this policy is > applied? If so, how do we do that? > > > Thanks, > Carl _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
