MeeGo applauncherd: faster application startup and more
alberto.mardegan at canonical.com
Mon Jun 17 12:58:32 UTC 2013
On 06/17/2013 04:14 PM, Marc Deslauriers wrote:
> Hrm, since this forks instead of doing an exec, it probably doesn't
> handle kernel security mechanisms well, such as ASLR. I'm not sure how
> we would handle switching AppArmor policies either, or how well our DBus
> AppArmor integration would work.
> Our current plan is to use Upstart for application launching.
I'm not sure about ASLR. But at least it should be possible to randomize
the loading address the first time that the booster is started (at boot
time, maybe?), or the booster can be killed and restarted from time to
time. Also, the loading address of the application executable could be
> Are there any benchmarks somewhere that show what the performance gains
> are on application startup using mapplauncherd?
I'couldn't find any, but the difference is so huge that you don't need
any benchmarks :-) Just watch this:
The second time, the applauncherd hasn't had the time to initialize a
new booster process, so a cold start-up happens instead.
More information about the ubuntu-devel