History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CCNET-504
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Craig Sutherland
Reporter: Jeff Bergren
Votes: 3
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
CruiseControl .NET

Process Priority setting for tasks

Created: 10/Aug/05 08:30 AM   Updated: 25/Jul/10 12:48 PM
Return to search
Issue 8 of 67 issue(s)
<< Previous | CCNET-504 | Next >>
Component/s: Task
Affects Version/s: 0.9.2, 1.0 RC1, 1.0 RC2, 1.0, 1.0.1, 1.1, 1.2, 1.1.1, 1.3, 1.2.1, 1.4, 1.4.1, 1.4.3, 1.4.2, 1.5.0 RC1, 1.4.4 RC1, 1.5.0 CTP, 1.4.4 RC2, 1.4.4, 1.4.4 SP1, 1.4.5
Fix Version/s: 1.5.0 RC1

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File 0001-Implement-process-priority-property-on-exec-tasks.patch (34 kb)
2. Text File 0001-Implement-process-priority-property-on-exec-tasks.patch (108 kb)
3. Text File priority 1.5.patch (32 kb)
4. Text File priority 1.5.patch (28 kb)
5. Text File priority.patch (17 kb)

Environment: Any


 Description  « Hide
It'd be helpful if the task could be set to run at a lower or higher process priority on the system.

We're using the server for more than CruiseControl and some of the builds bring the system to a stand-still, including processes like ASP.net. At times, one build causes other builds to time-out, checking modifications by CruiseControl slows down infinitely, etc.

Not sure if this feature would fix the problem however since NANT fires off it's tasks as separate processes. Haven't been able to try if the priority would carry over to these later spawned processes (which are the culprit in the end).

NANT may also need a priority setting on tasks.



 All   Comments   Work Log   Change History      Sort Order:
No work has yet been logged on this issue.