IZ2542: Allow users to limit concurrent array job task execution
|Reported by:||craffi||Owned by:|
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2542]
Issue #: 2542 Platform: All Reporter: craffi (craffi) Component: gridengine OS: All Subcomponent: scheduling Version: current CC: None defined Status: STARTED Priority: P2 Resolution: Issue type: ENHANCEMENT Target milestone: Maintrunk Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: Allow users to limit concurrent array job task execution Status whiteboard: Attachments: Issue 2542 blocks: Votes for issue 2542: Opened: Sun Apr 6 07:17:00 -0700 2008 ------------------------ Summary: - This RFE requests a way for users (who do not have administrative access to policy and RQS settings) to self-throttle the number of concurrent array tasks executing at any given time. In relation to these existing Enhancement issues: http://gridengine.sunsource.net/issues/show_bug.cgi?id=2147 http://gridengine.sunsource.net/issues/show_bug.cgi?id=1276 The desired behavior is the following: - Allow a user to limit the number of concurrent executing array tasks Issue: - Users have been trained to use array tasks to reduce SGE load - Users who do this typically submit very large array jobs via qsub - Users want to throttle concurrent execution of tasks to a fixed value - This "self throttle" control is desired at the user level (not policy or RQS level) A "task" target for resource quotas has already been written up in #2147 - this RFE asks for an extention to the "-t" switch of qsub: Existing array task syntax: -t n[-m[:s]] Proposed array task syntax: -t n[-m[:s]] -tc <INT> .. where "-tc" is shorthand for "task concurrency". The default value should place no constraint on executing tasks. If present, <INT> will specify the upper bound of tasks that are allowed to execute simultaneously. ------- Additional comments from andreas Mon Apr 7 00:34:00 -0700 2008 ------- Good RFE! It should be possible to reuse our existing RQS code infrastructure for it. I raise it to P2 as this was repeatedly requested by the community. It will improve SGE resource control significantly. ------- Additional comments from andreas Mon Apr 7 00:39:41 -0700 2008 ------- Target milestone obviously must be past 6.2. ------- Additional comments from templedf Mon Dec 22 23:43:05 -0700 2008 ------- Expanded platform to all.
Change History (1)
Note: See TracTickets for help on using tickets.