On Wed, Oct 07 2009, Petter Reinholdtsen wrote:
> [Manoj Srivastava]
>>> Is CONCURRENCY set in /etc/init.d/rc ? I used to have it set there.
>>
>> /etc/init.d/rc:CONCURRENCY=none
>
> Could it be a bootchart problem instead, graphing the wrong file or
> something? The version in unstable was bro
[Manoj Srivastava]
>> Is CONCURRENCY set in /etc/init.d/rc ? I used to have it set there.
>
> /etc/init.d/rc:CONCURRENCY=none
Could it be a bootchart problem instead, graphing the wrong file or
something? The version in unstable was broken because some Java
library changed its API. I uploaded
On Tue, Oct 06 2009, Felipe Sateler wrote:
> On Tue, 2009-10-06 at 09:50 +0200, Petter Reinholdtsen wrote:
>> [Manoj Srivastava]
>> > I rebooted, and I still get init.d/rc is starting startpar. I do
>> > not have any line with CONCURRENCY= in /etc/default/rcS, commented
>> > or otherwise. There
On Tue, 2009-10-06 at 09:50 +0200, Petter Reinholdtsen wrote:
> [Manoj Srivastava]
> > I rebooted, and I still get init.d/rc is starting startpar. I do
> > not have any line with CONCURRENCY= in /etc/default/rcS, commented
> > or otherwise. There is definitely a bug somewhere.
>
> Very strange.
[Manoj Srivastava]
> I rebooted, and I still get init.d/rc is starting startpar. I do
> not have any line with CONCURRENCY= in /etc/default/rcS, commented
> or otherwise. There is definitely a bug somewhere.
Very strange. This do not happen when I test without the CONCURRENCY
value set. Is th
On Mon, Oct 05 2009, Manoj Srivastava wrote:
> Well, I have commented it out; I'll try again to reboot after
> removing the line.
I rebooted, and I still get init.d/rc is starting startpar. I do
not have any line with CONCURRENCY= in /etc/default/rcS, commented or
otherwise. Th
Hi,
Well, I have commented it out; I'll try again to reboot after
removing the line.
manoj
#
# /etc/default/rcS
#
# Default settings for the scripts in /etc/rcS.d/
#
# For information about these variables see the rcS(5) manual page.
#
# This file belongs to the "initscripts" pa
[Manoj Srivastava]
> ok. Late, but better than never:
> http://people.debian.org/~srivasta/
Thank you. Very interesting to see. :)
> bootchart-unopt.png = Data from before I started working
> on optimizing boot times
Duration 2 minutes 13 s
On Fri, Sep 25 2009, Petter Reinholdtsen wrote:
> [Manoj Srivastava]
>> I can still put up the bootchartd data, but it is pretty boring.
> Please do, I find it interesting to learn more how different Debian
> systems boot to see if there are new improvements to be found. :)
ok. Late, but
[Manoj Srivastava]
> So, on deeper inspection, I have to recant: setting concurrency to
> makefile in /etc/default/rcS does not in fact change the
> timing. Which made me wonder why I thought it did, and it might be
> that I removed but not purged a package, and that might have made
> inserv
On Sat, Sep 12 2009, Petter Reinholdtsen wrote:
> [Michael Biebl]
>> Would be interesting to have a before and after bootchart so this
>> regression can be investigated.
>
> Yes, definitely. Would also be interesting to know what kind of
> hardware you got (CPU, harddrive), and if you enabled read
On Sun, Sep 20, 2009 at 13:52:59 -0700, lkcl wrote:
[...]
> some years back, richard lightman wrote depinit. it's a complete
> replacement for sysvinit, and it's a parallel initialisation system.
>
> unlike sysvinit, it caught _all_ signals on applications.
>
> i installed it several times, a
Petter Reinholdtsen wrote:
>
> One "hidden" feature of the current Debian boot sustem, is the ability
> to run the init.d scripts in parallel.
>
some years back, richard lightman wrote depinit. it's a complete
replacement for sysvinit, and it's a parallel initialisation system.
unlike sy
On Sat, Sep 12 2009, Petter Reinholdtsen wrote:
> [Michael Biebl]
>> Would be interesting to have a before and after bootchart so this
>> regression can be investigated.
>
> Yes, definitely. Would also be interesting to know what kind of
> hardware you got (CPU, harddrive), and if you enabled read
[Michael Biebl]
> Would be interesting to have a before and after bootchart so this
> regression can be investigated.
Yes, definitely. Would also be interesting to know what kind of
hardware you got (CPU, harddrive), and if you enabled readahead or
not.
Happy hacking,
--
Petter Reinholdtsen
-
Manoj Srivastava wrote:
>
> I actually lost 7 seconds, according to bootchard, by setting
> that.
Would be interesting to have a before and after bootchart so this regression can
be investigated.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe
On Fri, 11 Sep 2009, Olivier Bonvalet wrote:
> But combined with "readahead", there is no I/O bound during init.
> Most of needed files are preload.
Any initscripts that deal with devices will still be I/O bound. And the
current scheduler doesn't help (see current threads in LKML). You should
st
On Fri, Sep 11 2009, Wouter Verhelst wrote:
> On Thu, Sep 10, 2009 at 01:05:32PM +0200, Petter Reinholdtsen wrote:
>> If you want to test this feature in testing or unstable, use this
>> command:
>>
>> echo CONCURRENCY=makefile >> /etc/default/rcS
>>
>> It will enable makefile style concurrenc
Wouter Verhelst wrote:
> On Thu, Sep 10, 2009 at 01:05:32PM +0200, Petter Reinholdtsen wrote:
>> If you want to test this feature in testing or unstable, use this
>> command:
>>
>> echo CONCURRENCY=makefile >> /etc/default/rcS
>>
>> It will enable makefile style concurrency, and run N scripts in
[Wouter Verhelst]
> That seems suboptimal.
Could be. See the startpar program to see how the scripts are run in
parallel. Note that the boot is mostly CPU bound when readahead is
used, which you should use if you care about boot speed. :)
> If it actually is configurable, but you just didn't te
But combined with "readahead", there is no I/O bound during init.
Most of needed files are preload.
Wouter Verhelst a écrit :
On Thu, Sep 10, 2009 at 01:05:32PM +0200, Petter Reinholdtsen wrote:
If you want to test this feature in testing or unstable, use this
command:
echo CONCURRENCY=ma
On Thu, Sep 10, 2009 at 01:05:32PM +0200, Petter Reinholdtsen wrote:
> If you want to test this feature in testing or unstable, use this
> command:
>
> echo CONCURRENCY=makefile >> /etc/default/rcS
>
> It will enable makefile style concurrency, and run N scripts in
> parallel during boot, where
22 matches
Mail list logo
