On Tue, 26.05.15 09:49, Filipe Brandenburger (filbran...@google.com) wrote:
> Hi,
>
> On Sun, May 24, 2015 at 8:41 PM, cee1 wrote:
> > I tried ureadahead, but got following error:
> >
> > """write(2, "ureadahead: Error while tracing:"..., 59ureadahead: Error
> > while tracing: No such file or di
Hi,
On Sun, May 24, 2015 at 8:41 PM, cee1 wrote:
> I tried ureadahead, but got following error:
>
> """write(2, "ureadahead: Error while tracing:"..., 59ureadahead: Error
> while tracing: No such file or directory"""
>
> Needs an out-of-tree kernel patch?
Yes, ureadahead needs an out-of-tree ker
2015-05-20 1:01 GMT+08:00 Martin Pitt :
> Hey cee1,
>
> cee1 [2015-05-18 23:52 +0800]:
>> At the first glance, I find ureadahead has some difference compared
>> with the readahead once in systemd, IIRC:
>
> Yes, for sure. systemd's was improved quite a bit. ureadahead is
> mostly unmaintained, but
On Tue, May 19, 2015 at 5:39 PM, Cristian Rodríguez
wrote:
> On Mon, May 18, 2015 at 7:24 AM, cee1 wrote:
>> 2015-05-17 17:45 GMT+08:00 Martin Pitt :
>>> Hello cee,
>>>
>>> cee1 [2015-05-16 0:46 +0800]:
Thanks for the suggestion, it was other processes running in parallel
which presuma
On Mon, May 18, 2015 at 7:24 AM, cee1 wrote:
> 2015-05-17 17:45 GMT+08:00 Martin Pitt :
>> Hello cee,
>>
>> cee1 [2015-05-16 0:46 +0800]:
>>> Thanks for the suggestion, it was other processes running in parallel
>>> which presumably consuming lots of IO, after sending SIGSTOP at the
>>> first (an
Hey cee1,
cee1 [2015-05-18 23:52 +0800]:
> At the first glance, I find ureadahead has some difference compared
> with the readahead once in systemd, IIRC:
Yes, for sure. systemd's was improved quite a bit. ureadahead is
mostly unmaintained, but it works well enough so we didn't bother to
put work
On Mon, 18.05.15 18:24, cee1 (fykc...@gmail.com) wrote:
> 2015-05-17 17:45 GMT+08:00 Martin Pitt :
> > Hello cee,
> >
> > cee1 [2015-05-16 0:46 +0800]:
> >> Thanks for the suggestion, it was other processes running in parallel
> >> which presumably consuming lots of IO, after sending SIGSTOP at t
Hi Martin,
At the first glance, I find ureadahead has some difference compared
with the readahead once in systemd, IIRC:
1. ureadahead.service is in default.target, which means ureadahead
starts later than systemd's?
2. The original systemd readahead has "collect" and "replay" two
services, and t
Hello cee1,
cee1 [2015-05-18 18:24 +0800]:
> Does the readahead-*.service shipped with systemd work for you?
systemd dropped the builtin readahead in 217. It's reasonably easy to
get back by reverting the "drop readahead" patches, but carrying that
patch in packages is fairly intrusive. In Ubuntu
2015-05-17 17:45 GMT+08:00 Martin Pitt :
> Hello cee,
>
> cee1 [2015-05-16 0:46 +0800]:
>> Thanks for the suggestion, it was other processes running in parallel
>> which presumably consuming lots of IO, after sending SIGSTOP at the
>> first (and SIGCONT later), the unit loading time is decreased t
Hello cee,
cee1 [2015-05-16 0:46 +0800]:
> Thanks for the suggestion, it was other processes running in parallel
> which presumably consuming lots of IO, after sending SIGSTOP at the
> first (and SIGCONT later), the unit loading time is decreased to
> ~100ms.
You probably want to use some readah
Original Message-
>> From: systemd-devel [mailto:systemd-devel-
>> boun...@lists.freedesktop.org] On Behalf Of cee1
>> Sent: Wednesday, May 13, 2015 11:52 AM
>> To: systemd Mailing List
>> Subject: [systemd-devel] Reduce unit-loading time
>>
>> Hi a
On Wed, 13.05.15 17:51, cee1 (fykc...@gmail.com) wrote:
> Hi all,
>
> We're trying systemd to boot up an ARM board, and find systemd uses
> more than one second to load units.
>
> Comparing with the init of Android on the same board, it manages to
> boot the system very fast.
>
> We guess follo
Hi,
> -Original Message-
> From: systemd-devel [mailto:systemd-devel-
> boun...@lists.freedesktop.org] On Behalf Of cee1
> Sent: Wednesday, May 13, 2015 11:52 AM
> To: systemd Mailing List
> Subject: [systemd-devel] Reduce unit-loading time
>
> Hi all,
>
>
Hi all,
We're trying systemd to boot up an ARM board, and find systemd uses
more than one second to load units.
Comparing with the init of Android on the same board, it manages to
boot the system very fast.
We guess following factors are involved:
1. systemd has a much bigger footprint than the
15 matches
Mail list logo