You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hot reload "syncing files to device" takes a long time #6508
Re-compression: We are already using gzip compression over an HTTP put.
We might want to try bundling an initial version of the source into the APK/IPA.
Is this in reference to the initial copy of the files that happens before we start the application or the syncing of the remaining that happens while the app is launching? If it is the latter, I think we can make that faster by not doing it at all.
When the progress meter is on the device we do the following:
Use the snapshot binary to quickly determine the minimal set of Dart sources actually loaded by your program. We don't build a snapshot but rely on the VM's parser to determine the transitive import set. This is very fast.
Begin sending over the Dart sources via HTTP PUT compressed with gzip. This isn't that fast but I'm not sure what could be done to speed it up.
Send over all assets via HTTP PUT compressed with gzip. This isn't that fast but I'm not sure what could be done to speed it up.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
johnmccutchan commentedon Oct 27, 2016
Re-compression: We are already using gzip compression over an HTTP put.
We might want to try bundling an initial version of the source into the APK/IPA.
Is this in reference to the initial copy of the files that happens before we start the application or the syncing of the remaining that happens while the app is launching? If it is the latter, I think we can make that faster by not doing it at all.
Hixie commentedon Oct 27, 2016
This is in reference to the time you see the progress meter on the device.
But more broadly, my interest is in minimising the time from starting "flutter run" to having the device be responsive with your app loaded.
johnmccutchan commentedon Oct 27, 2016
When the progress meter is on the device we do the following:
Hixie commentedon Oct 27, 2016
How much data are we sending and what's the overall average data rate?
Add support for text shadows and roll engine (26 commits) (#22449)
github-actions commentedon Aug 15, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.