Opened 19 years ago

Last modified 11 years ago

#39 new enhancement

IZ256: optimization of search for objects

Reported by: joga Owned by:
Priority: normal Milestone:
Component: sge Version: 5.3
Severity: Keywords: cleanup


[Imported from gridengine issuezilla]

        Issue #:      256              Platform:     All           Reporter: joga (joga)
       Component:     gridengine          OS:        All
     Subcomponent:    cleanup          Version:      5.3              CC:    None defined
        Status:       STARTED          Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
       * Summary:     optimization of search for objects
   Status whiteboard:

     Issue 256 blocks:
   Votes for issue 256:

   Opened: Wed May 15 01:46:00 -0700 2002 

We have a lot of code searching sequentially
through lists comparing ids to find a certain object.

This code could be replaced by calls to

It would both improve readability and allow
optimization when hashing is enabled for the
search key attribute.

   ------- Additional comments from joga Wed Dec 18 03:19:01 -0700 2002 -------
The lGetElem<type>Next function itself could be improved:

Profiling shows that the check of input parameters done by
lGetElem<type>Next are quite expensive (especially getting the
position of the queried field and checking the data type) and not
really necessary: This information does not change between calls of
lGetElem<type>First and lGetElem<type>Next.

All information needed by the Next function could be stored in the
iterator: list, nm, pos, value, pointer to last found object.

   ------- Additional comments from ernst Tue Jun 10 23:48:38 -0700 2008 -------

Change History (0)

Note: See TracTickets for help on using tickets.