[ControlFlow][NewExe] set Flag_control_flow_use_new_executor=true by default #49447
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.
PR types
Others
PR changes
OPs
Describe
The support of
InterpreterCorewas added for control flow ops in #45696 and #47573.These changes were tested with model
paddlenlp.transformers.InferTransformerModel. The running scripts comes from here.Since the test results show that running control flow ops with
InterpreterCorehas no negative effect, we decide to make this a default behavior by setFlag_control_flow_use_new_executor's initial value totrue.Test Results
Speed
InterpreterCoreExecutorAccuracy
We printed the output
finished_sequenceof every step in both conditions and compared them.The output was exactly same no matter which executor was used.
Memory Usage
We printed max memory usage during execution of first ten steps:
InterpreterCoreExecutor