Skip to content

Investigate comments from Jukzi regarding full build #29

@fedejeanne

Description

@fedejeanne

See eclipse-jdt/eclipse.jdt.core#3411 (comment)

Please also note that the provided snapshot still contains hotspots that should not be there. for example spending 65 sec below org.eclipse.jdt.internal.core.builder.ClasspathDirectory.isPackage() does not make sense, so there should be much more room for optimization. or still 36 sec below org.eclipse.jdt.internal.compiler.lookup.TypeBinding.findSuperTypeOriginatingFrom () 12 sec below org.eclipse.osgi.internal.resolver.StateHelperImpl.getPackages () WTH

I hope you can contribute more performance improvements :-)

Investigate (at least) these and create the corresponding issues for them:

  • org.eclipse.jdt.internal.core.builder.ClasspathDirectory.isPackage() (65s)
  • org.eclipse.jdt.internal.compiler.lookup.TypeBinding.findSuperTypeOriginatingFrom () (36s)
  • org.eclipse.osgi.internal.resolver.StateHelperImpl.getPackages () (12s)

Metadata

Metadata

Assignees

No one assigned

    Labels

    JDTIssues for JDTPerformanceA Request for a Performance Improvement

    Type

    No type

    Projects

    Status

    🆕 New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions