[GE issues] [Issue 2843] New - The reprioritization code is inefficient and executed even if feature is disabled

roland roland.dittel at sun.com
Thu Dec 18 15:54:52 GMT 2008


http://gridengine.sunsource.net/issues/show_bug.cgi?id=2843
                 Issue #|2843
                 Summary|The reprioritization code is inefficient and executed 
                        |even if feature is disabled
               Component|gridengine
                 Version|6.2beta
                Platform|Sun
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P2
            Subcomponent|kernel
             Assigned to|roland
             Reported by|roland






------- Additional comments from roland at sunsource.net Thu Dec 18 07:54:48 -0800 2008 -------
The reprioritization code in qmaster is based on the tickets provided by the
scheduler.

1) The scheduler sends one ticket per job. For PE jobs one reprioritize request
needs to be send per host where the PE jobs run. For this the complete order
(which included several for reprioritization unnecessary files) was copied and
lead to a NxM relation. The qmaster grows unlinear with the slave tasks. A PE
job running on about 3000 nodes let the qmaster grow to about 2GB memory
2) The huge amount of datastructures that need to be send to the execds are
always created, even if reprioritize is disabled and therefore the data gets
trashed.

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

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



More information about the gridengine-users mailing list