I'll suggest the following for benchmarking the startup time:
$ time screen /bin/true
That should launch a screen session, run /bin/true, and exit immediately.
On my system (with all status enabled):
real 0m0.728s
It's about 2 seconds longer, if updates-available is required to run (ie, if the cache file is over an hour out of date).
I turned everything off and I get:
real 0m0.122s
Perhaps you can use this to find out which status is performing so poorly?
Also, you can disable the 'nice' commands by editing /usr/bin/screen-profiles-status and commenting out these two lines:
renice 10 $$ >/dev/null 2>&1 || true
ionice -c3 -p $$ >/dev/null 2>&1 || true
I'll suggest the following for benchmarking the startup time:
$ time screen /bin/true
That should launch a screen session, run /bin/true, and exit immediately.
On my system (with all status enabled):
real 0m0.728s
It's about 2 seconds longer, if updates-available is required to run (ie, if the cache file is over an hour out of date).
I turned everything off and I get:
real 0m0.122s
Perhaps you can use this to find out which status is performing so poorly?
Also, you can disable the 'nice' commands by editing /usr/bin/ screen- profiles- status and commenting out these two lines:
renice 10 $$ >/dev/null 2>&1 || true
ionice -c3 -p $$ >/dev/null 2>&1 || true
See if that makes things faster for you.
:-Dustin