fixed multiprocessing issue during RoBERTa prediction - Solution to #1558#1559
Open
etqadkhan wants to merge 1 commit intoThilinaRajapakse:masterfrom
Open
fixed multiprocessing issue during RoBERTa prediction - Solution to #1558#1559etqadkhan wants to merge 1 commit intoThilinaRajapakse:masterfrom
etqadkhan wants to merge 1 commit intoThilinaRajapakse:masterfrom
Conversation
|
Faced a similar issue and am glad to have found your workaround, im surprised this have not been pushed after a year. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With reference to #1558
When using a RoBERTa model for doing prediction, when the model is loaded using
ClassificationModel()it prompts a warning stating,When prediction is performed on text data, if the number of records are a little more than a handful, the prediction progress bar takes infinite execution.
The issue occurs because in the
classification_model.pyfile under theClassificationModelclass, there are two arguments that concern with multiprocessing, them being,args.use_multiprocessingandargs.use_multiprocessing_for_evaluation. While one is set to False by default, the other remains to be True,as can be seen in the screenshot attached:To be able to perform prediction by successfully disabling multiprocessing, we need to disable
args.use_multiprocessing_for_evaluation = Falseand it should work fine. The approach has been tested locally and has proven to be working. Screenshot attached: