Improve the performance of Obj.getType() by caching Obj's type
          #205
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
For huge programs such as
columba-1.4from java-benchmarks, most of the analysis time is spent onTypeFilterwhen propagating objects through the PFG, among which a major proportion is spent on theObj.getType().Simply caching the type of the
Objusing a field brings substantial speedup to the original Tai-e (comparing 8504562 to 064801b). On my laptop (AMD Ryzen7 4800H 2.9GHz with 16G heap memory for JVM) this optimization saves 30% of the analysis time forcolumba-1.4.Tai-e/src/main/java/pascal/taie/analysis/pta/core/heap/Obj.java
Lines 36 to 44 in 8504562
The results are shown below (irrelevant lines are removed for clarity):
log file for gettype optimization(8504562)
log file for master(064801b)