what if native systemd service is slower than old sysvinit script?

[drago01]

On Wed, Sep 14, 2011 at 5:34 PM, Ralf Corsepius <rc040203 at freenet.de> wrote:
> On 09/14/2011 04:31 PM, drago01 wrote:
>> On Wed, Sep 14, 2011 at 4:22 PM, Richard W.M. Jones<rjones at redhat.com>  wrote:
>>> On Wed, Sep 14, 2011 at 01:03:04AM +0200, Michał Piotrowski wrote:
>>>> Hi
>>>>
>>>> 2011/9/13 Tom Lane<tgl at redhat.com>:
>>>>> (This isn't new with 9.1, btw --- the last version or so of 9.0
>>>>> for F16 was the same, since we switched over to native systemd
>>>>> files.)
>>>>
>>>> I used this service file on F15 and it starts slower
>>>>    4214ms postgresql.service
>>>>
>>>> if we compare with an old SysVinit script
>>>>    2469ms postgresql.service
>>>>
>>>> So I wonder if it makes sense to convert in such case?
>>>>
>>>> (I know that it is not about boot speed, it can start slower if needed.)
>>>
>>> Is systemd boot actually any faster?
>
> Not from my personal experience.
>
>>>  There seems to be no
>>> noticable difference in boot times for me over whatever we
>>> were using in F14.  ie. both methods still takes ages, far
>>> longer than should be necessary.
>>
>> My laptop (using a Samsung ssd) booted up in 14-16 seconds on F14. Now
>> (F15) it boots up in 7-8 seconds. Which is a rather huge boost. (Not
>> using lvm or any fancy stuff).
>
> My netbook boots up F14 in ca. 60 secs, while F15 boots up in 62 secs.
> I'd call this "below measurement accuracy".

What kind of disk is that? For a mechanical drive any gain from
parallel startup  would get killed by disk seeks.