-
Notifications
You must be signed in to change notification settings - Fork 30
Implementation of several scheduling methods to improve the performance of static analyses #263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
…se can run without exception
This reverts commit 0d3ba57.
…erTest.scala eingepflegt, erste Anfänge Purity anzupassen
# Conflicts: # DEVELOPING_OPAL/tools/src/main/scala/org/opalj/support/info/Immutability.scala # OPAL/si/src/main/scala/org/opalj/fpcf/seq/PKESequentialPropertyStore.scala
…debugging purposes ONLY!
…es at once. Old immutability with manual batching is also included in the folder
…asurement # Conflicts: # OPAL/tac/src/main/scala/org/opalj/tac/fpcf/analyses/cg/DoPrivilegedCGAnalysis.scala
…r the handleNewCallers method in the FieldLocalityAnalysis.scala
OPAL/si/src/test/scala/org/opalj/fpcf/PropertyComputationsSchedulerTest.scala
Outdated
Show resolved
Hide resolved
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has taken a significant step forward, but now that I could take a clearer look at the strategies, some more (minor) issues surfaced. Expect a few more one the duplicated code is extracted, since I will review it once I can clearly see the differences between the strategies vs. what is common.
Static subanalyses are divided into different batches and summarized by the strategies in order to shorten the runtime.
This approach offers 4 strategies:
Single Phase Scheduling (SPS) - All sub-analyses are put into one batch and executed (may lead to wrong results in some cases. Further research needed).
Maximum Phase Scheduling (MP)- This strategy tries to create the most phases from the given analyses.
Independent Phase Merge Scheduling (IPMS) - An extension of the MPS strategy that executes independent phases together.
Smallest Phase Merge Scheduling (SPMS) - Also an extension of the MPS strategy, which merges independent phases into one phase based on the number of partial analyses.
There is also a Lazy Transformer Multiple Phase Flag, which allows the analyses to schedule lazy and transformer partial analyses in multiple phases.