Descoping BERT for mobile #34
Merged
Conversation
This file contains 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.
Although the majority of "BERT for Mobile" is complete it appears that there are still some unclarities in the model conversions for MobileBERT and ALBERT i.e. the converted models aren't able to produce expected results (drop from original 90% to 49%). Note that when a MobileBERT model is fine-tuned using the Model Maker tool the performance is greatly retained. This is indeed weird actually.
Unfortunately, the TFLite team currently has other competing priorities so they may not be able to take a look at this issue. So, with these unclarities, I don't feel comfortable publishing the blog post. I Will update accordingly when things start to move in the right direction.