Opened 12 years ago
Last modified 10 years ago
#599 new defect
IZ2802: Classic spooling operations for sequential jobs could be more efficient
Reported by: | andreas | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2 |
Severity: | Keywords: | qmaster | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2802]
Issue #: 2802 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: qmaster Version: 6.2 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: ernst (ernst) QA Contact: ernst URL: * Summary: Classic spooling operations for sequential jobs could be more efficient Status whiteboard: Attachments: Issue 2802 blocks: Votes for issue 2802: Opened: Fri Nov 21 04:28:00 -0700 2008 ------------------------ Classic spooling operations for sequential jobs could be more efficient (1) At job submission time the mkdir() is needed, but no the dot-file writing plus rename() (2) Any operation after job submission needs the dot-file writing plus rename(), but not the mkdir() Conclusion is this: It is possible to make classic spooling for sequential jobs more efficient, if the code that controls dot-file writing plus rename() and the mkdir() can differ between the cases (1) and (2)
Note: See
TracTickets for help on using
tickets.