Fix recompilation when batch processing is not triggered #447
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.
Description
This patch provides a fix to avoid continuous recompilation of execution plans that do not use batch processing.
TornadoVM was set to recompile every time, but we only need to recompile under certain conditions only when using batch processing, or when changing the device.
Side note: We need the benchmarking suite for the AERO project.
Problem description
The issue was that the benchmark suite, and therefore, user code, can trigger recompilation over and over again due to a condition for batch processing.
Backend/s tested
Mark the backends affected by this PR.
OS tested
Mark the OS where this PR is tested.
Did you check on FPGAs?
If it is applicable, check your changes on FPGAs.
How to test the new patch?