[Android-development] Warm application start time
developer at lagner.ru
Tue Jun 14 21:31:09 CEST 2016
Thank you for advice
We are already doing our best to optimize QML loading time. We use Loaders
from QML side
and lazy loading for models from C++ side. But the application still too
It takes 6 sec approximately to launch on Nexus 5.
Therefore we are looking for other ways to improve our app.
Now I'm care about warm start.
Lets consider the following scenario:
- I launch the app. It takes 6 sec.
- Press back and see a home screen
- Launch the app again in a second. And again it takes 6 sec.
That is mean that all resources were freed and second start was completely
I wonder if I could speed up the second(warm) start from java side.
For example, is it possible so save preloaded native libraries until the OS
has the real lack of memory?
2016-06-14 21:56 GMT+06:00 Xavier Bigand <flamaros.xavier at gmail.com>:
> If you are using QML you may have to use Loaders to avoid loading of GUI
> parts that are not displayed directly.
> You can also take a look to the QtQuick compiler to improve qml loading.
> There is a profiler on QtCreator for QML which can help you to find your
> binding that are slow, be sure to not having binding loops.
> 2016-06-14 16:33 GMT+02:00 Лагнер, Сергей <developer at lagner.ru>:
>> Hi all.
>> I'm trying to optimize start time of my android application. For now I'm
>> interested in warm start time
>> when the user presses back and quickly returns to the app. If we consider
>> java application the
>> warm start is faster, it seems like android caches something or so.
>> But it does not work for Qt applications. My application spends constant
>> time for each start, even if I closed it a second ago.
>> Is there any way to optimize warm start of Qt application?
>> Any hints are highly appreciated.
>> Android-development mailing list
>> Android-development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Android-development