Opened 14 years ago

Last modified 8 years ago

#232 new enhancement

IZ1499: Enhance recomputation of consumables

Reported by: joga Owned by:
Priority: low Milestone:
Component: sge Version: current
Severity: Keywords: cleanup
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=1499]

        Issue #:      1499             Platform:     All           Reporter: joga (joga)
       Component:     gridengine          OS:        All
     Subcomponent:    cleanup          Version:      current          CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
          URL:
       * Summary:     Enhance recomputation of consumables
   Status whiteboard:
      Attachments:

     Issue 1499 blocks:
   Votes for issue 1499:


   Opened: Tue Mar 15 03:47:00 -0700 2005 
------------------------


When a complex variable is modified, a recomputation of the resource debitation
may be required.
This is the case, when a variable has been changed from non consumable to
consumable and vice versa, or when the default request of a consumable is changed.

In this case, the current implementation trashes the resource debitation of all
hosts and queues and recomputes all values.

It would only be necessary to trash and recompute the values for the affected
hosts and queues (where the consumable is actually configured). Only the
debitation for the affected variables has to be recomputed.

This would significantly improve performance of this action, as
- all affected queue instances are spooled
- the version number of affected queues is increased, which means that
scheduling decisions that have been made on the old queue version will not be
accepted and have to be repeated.

As the situation in which a recomputation is required, is not really a frequent
one, I consider it being a P4 issue.

Change History (0)

Note: See TracTickets for help on using tickets.