Title:
Bug 72730:(Watson Migration Closure)Provide Scheduled Task Resource Pools / Minimums
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Ben Davies / Ben Davies (Ben Davies)
Created: 08/19/2008
Components: Scheduler
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Most users will encounter
Locale/System: English / Win All
Vote Count: 0
Problem:
Provide Scheduled Task Resource Pools / Minimums
If catch up scheduling is implemented, or if environmental conditions on the servers are highly variable based on intensive operations, it would be nice to be able to allocate scheduled tasks to resource pools or otherwise restrict when they run dependent on other server activities.
The simplest approach would be to allow the user to define a resource pool, which is simply a name, against a task. If another scheduled task is running with the same resource pool name, delay execution until it is complete or until the next scheduled time (which implies catch-up scheduling: ER #72729)
A more complex approach would be to provide a value for resource pool usage along with a name, depending on the load introduced by the task. For example, you might want to run 2 light tasks at the same time, but only 1 heavy task, for a specific resource pool.
Another approach would be to simply specify machine states such as ram and requests per second that are required before the task kicks off.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3035858
External Customer Info:
External Company:
External Customer Name: Ben Davies
External Customer Email: 447227C844C7765A992015A8
External Test Config: 08/19/2008Attachments:
Comments: