[GE issues] [Issue 2805] New - Task spooling always causes job be spooled as well for array jobs with classic spooling

andreas andreas.haas at sun.com
Fri Nov 21 12:20:04 GMT 2008


http://gridengine.sunsource.net/issues/show_bug.cgi?id=2805
                 Issue #|2805
                 Summary|Task spooling always causes job be spooled as well for
                        | array jobs with classic spooling
               Component|gridengine
                 Version|6.2
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|qmaster
             Assigned to|ernst
             Reported by|andreas






------- Additional comments from andreas at sunsource.net Fri Nov 21 04:20:00 -0800 2008 -------
When tasks state changes are spooled to disk as to make the state changes
persistent job data structure gets always spooled as well. This overhead however
exists with classic spooling only. With BerkeleyDB spooling task and job
operations are nicely disjunct which means that no more IO operations are
performed than necessary.

The classic spooling code that causes the overhead is located in function
job_write_spool_file() libs/spool/classic/read_write_job.c

     ret = job_write_common_part(job, ja_taskid, flags);
      if (!ret && !ignore_instances) {
         ret = job_write_ja_task_part(job, ja_taskid, pe_task_id, flags);
      }

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=36&dsMessageId=89347

To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list