Re: [android-developers] Re: Time to first screen, boot-up time and app-start time?
Hi, Is this user space start time ? I/boot_progress_start( 987): 5936 You said that I/boot_progress_start process start time may vary based on the hardware performance...you meant eMMC or cpu ? Could you please help me to understand each boot process here ? what it does exactly ? On Wednesday, 26 August 2009 06:52:21 UTC+5:30, Dianne Hackborn wrote: > > Here the standard log events during a boot showing the time (in ms) to get > to each point. This is on a myTouch class device, so should be similar on > a G1 etc. In the log, pms == package manager service (which keeps track of > all .apks), and ams == activity manager service. At the point where the > ams is ready we start launching application processes like home. There is > another 15-20 seconds not accounted for here which is the time from > pressing power until the kernel comes up enough for its timers to start (so > that time is basically like the BIOS boot time on a PC and unrelated to > Android). > > I/boot_progress_start( 51): 13897 > I/boot_progress_preload_start( 51): 18251 > I/boot_progress_preload_end( 51): 32464 > I/boot_progress_system_run( 81): 34178 > I/boot_progress_pms_start( 81): 34939 > I/boot_progress_pms_system_scan_start( 81): 35927 > I/boot_progress_pms_data_scan_start( 81): 44650 > I/boot_progress_pms_scan_end( 81): 44658 > I/boot_progress_pms_ready( 81): 44884 > I/boot_progress_ams_ready( 81): 48010 > I/boot_progress_enable_screen( 81): 57851 > > Of course, this all very much depends on the hardware you are running on. > For example, here are the times from another device I happen to have on my > desk: > > I/boot_progress_start( 987): 5936 > I/boot_progress_preload_start( 987): 8338 > I/boot_progress_preload_end( 987): 12915 > I/boot_progress_system_run( 1038): 13706 > I/boot_progress_pms_start( 1038): 14041 > I/boot_progress_pms_system_scan_start( 1038): 14372 > I/boot_progress_pms_data_scan_start( 1038): 18209 > I/boot_progress_pms_scan_end( 1038): 18211 > I/boot_progress_pms_ready( 1038): 18314 > I/boot_progress_ams_ready( 1038): 19983 > I/boot_progress_enable_screen( 1038): 23912 > > On Tue, Aug 25, 2009 at 2:27 PM, mst...@googlemail.com < > mst...@googlemail.com > wrote: > >> >> Thanks Chris! >> >> Some questions regarding your response: >> >> Do you know the reason why Android is so slow on start-up? Do you >> think it's possible to speed up Android by preventing certain >> applications loading by default and applying some of the fast booting >> improvements in order to drastically decrease boot-up time? I just >> found an article saying boot-up time is normally >10 sec. >> >> Is it actually the booting process of the kernel, start-up of the >> dalvik vm or application start-up which takes so long? >> >> Matthias >> >> On Aug 25, 9:09 pm, Chris Stratton wrote: >> > On Aug 25, 4:39 am, "mstu...@googlemail.com" >> > wrote: >> > >> > > at the moment I am thinking about a new app and need some information >> > > to decide whether to develop on Android or an alternative OS. >> > >> > > I am particularly interested in "time to first screen", "boot-up >> > > time", "time to first Audio" and "app-start" (can be any from the >> > > android market or even one of the pre-installed ones) time? Does >> > > anyone know a source or perhaps measured those numbers? >> > >> > If you literally want to be booting the operating system often, I >> > don't think you want android but some more simplistic embedded linux >> > with some of the recent generic-linux fast booting improvements >> > applied. Android is pretty slow to start up after a power cycle or >> > true reset, but the devices it is running on don't usually get turned >> > off very often, they just move between sleep and wake states. >> >> > > > -- > Dianne Hackborn > Android framework engineer > hac...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Time to first screen, boot-up time and app-start time?
Of course it is possible... the question is by how much, and with how much work. Those questions are difficult to answer though without actually digging into the code and starting to look at what it is doing and what can be improved. The numbers I gave should serve as a good guide for where to start looking first for the most bang for the buck. On Wed, Aug 26, 2009 at 12:25 PM, mstu...@googlemail.com < mstu...@googlemail.com> wrote: > > Hi All, > > thanks for all the comments... > > I am just wondering whether it is generally possible to speed up start > time? > > For instance, is it possible to apply some of the recent generic-linux > fast booting improvements to Android? If so, only the Kernel boot time > could be shortened... > > But what abt the other time-consuming "components" such as the PMS and > AMS... I don't see any options to optimize them... > > mat > > On Aug 26, 8:23 am, Dan Bornstein wrote: > > On Tue, Aug 25, 2009 at 5:02 PM, Casper Bang > wrote: > > > People who have digged into Dalvik aren't > > > overly impressed when compared to similar technologies: > > >http://www.koushikdutta.com/2009/01/dalvik-vs-mono.html > > > > Please read the comments on that article, which contained some good > > discussion, and please be aware that the original author is pushing a > > particular agenda. (Not that I don't have my own biases too, but I > > think I am reasonablyup-front about them.) > > > > -dan > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
Hi All, thanks for all the comments... I am just wondering whether it is generally possible to speed up start time? For instance, is it possible to apply some of the recent generic-linux fast booting improvements to Android? If so, only the Kernel boot time could be shortened... But what abt the other time-consuming "components" such as the PMS and AMS... I don't see any options to optimize them... mat On Aug 26, 8:23 am, Dan Bornstein wrote: > On Tue, Aug 25, 2009 at 5:02 PM, Casper Bang wrote: > > People who have digged into Dalvik aren't > > overly impressed when compared to similar technologies: > >http://www.koushikdutta.com/2009/01/dalvik-vs-mono.html > > Please read the comments on that article, which contained some good > discussion, and please be aware that the original author is pushing a > particular agenda. (Not that I don't have my own biases too, but I > think I am reasonablyup-front about them.) > > -dan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
On Tue, Aug 25, 2009 at 5:02 PM, Casper Bang wrote: > People who have digged into Dalvik aren't > overly impressed when compared to similar technologies: > http://www.koushikdutta.com/2009/01/dalvik-vs-mono.html Please read the comments on that article, which contained some good discussion, and please be aware that the original author is pushing a particular agenda. (Not that I don't have my own biases too, but I think I am reasonably up-front about them.) -dan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
Here the standard log events during a boot showing the time (in ms) to get to each point. This is on a myTouch class device, so should be similar on a G1 etc. In the log, pms == package manager service (which keeps track of all .apks), and ams == activity manager service. At the point where the ams is ready we start launching application processes like home. There is another 15-20 seconds not accounted for here which is the time from pressing power until the kernel comes up enough for its timers to start (so that time is basically like the BIOS boot time on a PC and unrelated to Android). I/boot_progress_start( 51): 13897 I/boot_progress_preload_start( 51): 18251 I/boot_progress_preload_end( 51): 32464 I/boot_progress_system_run( 81): 34178 I/boot_progress_pms_start( 81): 34939 I/boot_progress_pms_system_scan_start( 81): 35927 I/boot_progress_pms_data_scan_start( 81): 44650 I/boot_progress_pms_scan_end( 81): 44658 I/boot_progress_pms_ready( 81): 44884 I/boot_progress_ams_ready( 81): 48010 I/boot_progress_enable_screen( 81): 57851 Of course, this all very much depends on the hardware you are running on. For example, here are the times from another device I happen to have on my desk: I/boot_progress_start( 987): 5936 I/boot_progress_preload_start( 987): 8338 I/boot_progress_preload_end( 987): 12915 I/boot_progress_system_run( 1038): 13706 I/boot_progress_pms_start( 1038): 14041 I/boot_progress_pms_system_scan_start( 1038): 14372 I/boot_progress_pms_data_scan_start( 1038): 18209 I/boot_progress_pms_scan_end( 1038): 18211 I/boot_progress_pms_ready( 1038): 18314 I/boot_progress_ams_ready( 1038): 19983 I/boot_progress_enable_screen( 1038): 23912 On Tue, Aug 25, 2009 at 2:27 PM, mstu...@googlemail.com < mstu...@googlemail.com> wrote: > > Thanks Chris! > > Some questions regarding your response: > > Do you know the reason why Android is so slow on start-up? Do you > think it's possible to speed up Android by preventing certain > applications loading by default and applying some of the fast booting > improvements in order to drastically decrease boot-up time? I just > found an article saying boot-up time is normally >10 sec. > > Is it actually the booting process of the kernel, start-up of the > dalvik vm or application start-up which takes so long? > > Matthias > > On Aug 25, 9:09 pm, Chris Stratton wrote: > > On Aug 25, 4:39 am, "mstu...@googlemail.com" > > wrote: > > > > > at the moment I am thinking about a new app and need some information > > > to decide whether to develop on Android or an alternative OS. > > > > > I am particularly interested in "time to first screen", "boot-up > > > time", "time to first Audio" and "app-start" (can be any from the > > > android market or even one of the pre-installed ones) time? Does > > > anyone know a source or perhaps measured those numbers? > > > > If you literally want to be booting the operating system often, I > > don't think you want android but some more simplistic embedded linux > > with some of the recent generic-linux fast booting improvements > > applied. Android is pretty slow to start up after a power cycle or > > true reset, but the devices it is running on don't usually get turned > > off very often, they just move between sleep and wake states. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
Yeah it might not be terribly important, but it does leave a bad impression when showcasing the device. I mean, my Magic takes 1min 10sec to get to the SIM-unlock screen. A full fledged Ubuntu *nix takes about 40 sec, iPhone *nix about 42 sec and Samsung 10" wifi picture frame *nix takes about 20 sec. I have always been wondering whether it's the Dalvik VM that does it, considering that Java applications in general aren't exactly known for their rapid startup times. People who have digged into Dalvik aren't overly impressed when compared to similar technologies: http://www.koushikdutta.com/2009/01/dalvik-vs-mono.html /Casper On 26 Aug., 01:29, "Yusuf Saib (T-Mobile USA)" wrote: > The Android OS takes a long time to boot, particularly on a device > which is much slower than a desktop. Apps don't take so long. Android > was designed to do other things well; boot time doesn't appear to be a > priority. There is plenty of info on how to boot Linux fast, both on > devices > (http://moblin.org/projects/fast-bootandhttp://www.mvista.com/sol_detail_mobile.php) > and in general (http:// > lwn.net/Articles/299483/). It depends on your priorities. Of course if > you could optimize Android's boot time AND get Google to accept the > patch, all the better. > > Yusuf Saib > Android > ·T· · ·Mobile· stick together > The views, opinions and statements in this email are those of the > author solely in their individual capacity, and do not necessarily > represent those of T-Mobile USA, Inc. > > On Aug 25, 2:27 pm, "mstu...@googlemail.com" > wrote: > > > Thanks Chris! > > > Some questions regarding your response: > > > Do you know the reason why Android is so slow on start-up? Do you > > think it's possible to speed up Android by preventing certain > > applications loading by default and applying some of the fast booting > > improvements in order to drastically decrease boot-up time? I just > > found an article saying boot-up time is normally >10 sec. > > > Is it actually the booting process of the kernel, start-up of the > > dalvik vm or application start-up which takes so long? > > > Matthias > > > On Aug 25, 9:09 pm, Chris Stratton wrote: > > > > On Aug 25, 4:39 am, "mstu...@googlemail.com" > > > wrote: > > > > > at the moment I am thinking about a new app and need some information > > > > to decide whether to develop on Android or an alternative OS. > > > > > I am particularly interested in "time to first screen", "boot-up > > > > time", "time to first Audio" and "app-start" (can be any from the > > > > android market or even one of the pre-installed ones) time? Does > > > > anyone know a source or perhaps measured those numbers? > > > > If you literally want to be booting the operating system often, I > > > don't think you want android but some more simplistic embedded linux > > > with some of the recent generic-linux fast booting improvements > > > applied. Android is pretty slow to start up after a power cycle or > > > true reset, but the devices it is running on don't usually get turned > > > off very often, they just move between sleep and wake states. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
The Android OS takes a long time to boot, particularly on a device which is much slower than a desktop. Apps don't take so long. Android was designed to do other things well; boot time doesn't appear to be a priority. There is plenty of info on how to boot Linux fast, both on devices (http://moblin.org/projects/fast-boot and http://www.mvista.com/sol_detail_mobile.php) and in general (http:// lwn.net/Articles/299483/). It depends on your priorities. Of course if you could optimize Android's boot time AND get Google to accept the patch, all the better. Yusuf Saib Android ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 25, 2:27 pm, "mstu...@googlemail.com" wrote: > Thanks Chris! > > Some questions regarding your response: > > Do you know the reason why Android is so slow on start-up? Do you > think it's possible to speed up Android by preventing certain > applications loading by default and applying some of the fast booting > improvements in order to drastically decrease boot-up time? I just > found an article saying boot-up time is normally >10 sec. > > Is it actually the booting process of the kernel, start-up of the > dalvik vm or application start-up which takes so long? > > Matthias > > On Aug 25, 9:09 pm, Chris Stratton wrote: > > > > > On Aug 25, 4:39 am, "mstu...@googlemail.com" > > wrote: > > > > at the moment I am thinking about a new app and need some information > > > to decide whether to develop on Android or an alternative OS. > > > > I am particularly interested in "time to first screen", "boot-up > > > time", "time to first Audio" and "app-start" (can be any from the > > > android market or even one of the pre-installed ones) time? Does > > > anyone know a source or perhaps measured those numbers? > > > If you literally want to be booting the operating system often, I > > don't think you want android but some more simplistic embedded linux > > with some of the recent generic-linux fast booting improvements > > applied. Android is pretty slow to start up after a power cycle or > > true reset, but the devices it is running on don't usually get turned > > off very often, they just move between sleep and wake states. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
Thanks Chris! Some questions regarding your response: Do you know the reason why Android is so slow on start-up? Do you think it's possible to speed up Android by preventing certain applications loading by default and applying some of the fast booting improvements in order to drastically decrease boot-up time? I just found an article saying boot-up time is normally >10 sec. Is it actually the booting process of the kernel, start-up of the dalvik vm or application start-up which takes so long? Matthias On Aug 25, 9:09 pm, Chris Stratton wrote: > On Aug 25, 4:39 am, "mstu...@googlemail.com" > wrote: > > > at the moment I am thinking about a new app and need some information > > to decide whether to develop on Android or an alternative OS. > > > I am particularly interested in "time to first screen", "boot-up > > time", "time to first Audio" and "app-start" (can be any from the > > android market or even one of the pre-installed ones) time? Does > > anyone know a source or perhaps measured those numbers? > > If you literally want to be booting the operating system often, I > don't think you want android but some more simplistic embedded linux > with some of the recent generic-linux fast booting improvements > applied. Android is pretty slow to start up after a power cycle or > true reset, but the devices it is running on don't usually get turned > off very often, they just move between sleep and wake states. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Time to first screen, boot-up time and app-start time?
On Aug 25, 4:39 am, "mstu...@googlemail.com" wrote: > at the moment I am thinking about a new app and need some information > to decide whether to develop on Android or an alternative OS. > > I am particularly interested in "time to first screen", "boot-up > time", "time to first Audio" and "app-start" (can be any from the > android market or even one of the pre-installed ones) time? Does > anyone know a source or perhaps measured those numbers? If you literally want to be booting the operating system often, I don't think you want android but some more simplistic embedded linux with some of the recent generic-linux fast booting improvements applied. Android is pretty slow to start up after a power cycle or true reset, but the devices it is running on don't usually get turned off very often, they just move between sleep and wake states. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
