[jbosstools-issues] [JBoss JIRA] (ERT-666) Improve JDT Indexer performance for method reference lookups

[Roland Grunberg (JIRA)]

     [ https://issues.jboss.org/browse/ERT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roland Grunberg updated ERT-666:
--------------------------------
    Description: 
Based on discussions with Igor, various proposals were made to improve the method reference lookup times of the JDT Indexer.

One particular suggestion, which should be possible, with least amount of friction, would be to provide more information about the declaring type of a method in the indexer format.

The methodRef category table currently stores :

(symbol, number of arguments) -> document numbers (classfiles)
toString/0 -> [1, 4, 5, 25]

The proposal would change this to :

(symbol, symbol's classname, classname) -> document numbers (classfiles)
toString/0/java.lang.Object -> [1, 4, 5, 25]

Doing so should reduce the number of post-processing changes needed to verify that the declaring type of the first set of matches corresponds to the declaring type of the selected reference.

(/) Make the patch mostly correct
(?) Handle some more difficult corner cases (eg. detect references even to dead code)
(/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString()
(?) More complicated performance test against the Eclipse Platform itself for java.lang.Object.toString()
(?) A more thorough correctness test to identify any additional differences. (eg. test every single possible method reference, not just toString() )

  was:
Based on discussions with Igor, various proposals were made to improve the method reference lookup times of the JDT Indexer.

One particular suggestion, which should be possible, with least amount of friction, would be to provide more information about the declaring type of a method in the indexer format.

The methodRef category table currently stores :

(symbol, number of arguments) -> document numbers (classfiles)
toString/0 -> [1, 4, 5, 25]

The proposal would change this to :

(symbol, symbol's classname, classname) -> document numbers (classfiles)
toString/0/java.lang.Object -> [1, 4, 5, 25]

Doing so should reduce the number of post-processing changes needed to verify that the declaring type of the first set of matches corresponds to the declaring type of the selected reference.



> Improve JDT Indexer performance for method reference lookups
> ------------------------------------------------------------
>
>                 Key: ERT-666
>                 URL: https://issues.jboss.org/browse/ERT-666
>             Project: Eclipse Release Train
>          Issue Type: Task
>            Reporter: Roland Grunberg
>            Assignee: Roland Grunberg
>
> Based on discussions with Igor, various proposals were made to improve the method reference lookup times of the JDT Indexer.
> One particular suggestion, which should be possible, with least amount of friction, would be to provide more information about the declaring type of a method in the indexer format.
> The methodRef category table currently stores :
> (symbol, number of arguments) -> document numbers (classfiles)
> toString/0 -> [1, 4, 5, 25]
> The proposal would change this to :
> (symbol, symbol's classname, classname) -> document numbers (classfiles)
> toString/0/java.lang.Object -> [1, 4, 5, 25]
> Doing so should reduce the number of post-processing changes needed to verify that the declaring type of the first set of matches corresponds to the declaring type of the selected reference.
> (/) Make the patch mostly correct
> (?) Handle some more difficult corner cases (eg. detect references even to dead code)
> (/) Basic performance test with just a JVM target platform, and lookup of java.lang.Object.toString()
> (?) More complicated performance test against the Eclipse Platform itself for java.lang.Object.toString()
> (?) A more thorough correctness test to identify any additional differences. (eg. test every single possible method reference, not just toString() )



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)