From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A6E821381F4 for ; Fri, 17 Aug 2012 12:19:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FFAC21C078 for ; Fri, 17 Aug 2012 12:19:08 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 36D07E07C5 for ; Fri, 17 Aug 2012 11:56:10 +0000 (UTC) Received: by bkwj4 with SMTP id j4so1575582bkw.40 for ; Fri, 17 Aug 2012 04:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Vb7JPCjrEtKcAvXlkJ8AgJDRgvEWK7fi4CuZljnYL1U=; b=Y51Zyx4MNR7i1ZBRuzNp0BFOASAAoolH5pz+mzxCrZx79i+NiXMgB4MsrW2TaO51CE j9ORIJnVT5oy5mT+JiqfxVS1cmAzo2Y9AYujnHYaOabK4Ns5Hhb+1PA71cGXzTku3LGB t0qivOsB+ChZf7WjPVyKJOYyh1+HU4DgbP8DH0Pb80ikcNxmjVnrM0YkljJ9NEsID/+L dUe2yu2b2KmzPGQ/JI8nZpsbSls0GdP7HC7uBbqAzHLP2D3YFKLbKy2b/l9+ZeILsNbM zrMBL7BPAGDarbBtt+QCz4bEuqZ2DJr0vjOqErLK1iBggU3s1WjflyuE0EgUoE3jInfx keLg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.154.141 with SMTP id o13mr1715428bkw.72.1345204570196; Fri, 17 Aug 2012 04:56:10 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.204.14.76 with HTTP; Fri, 17 Aug 2012 04:56:10 -0700 (PDT) In-Reply-To: <502DF2C5.5090209@gentoo.org> References: <86wr1tcz8f.fsf@gmail.com> <86d333cngt.fsf@gmail.com> <5020DD0A.3030506@gentoo.org> <86ipct6k80.fsf_-_@gmail.com> <50235319.5000504@gentoo.org> <867gt75uab.fsf_-_@gmail.com> <5024CB9F.4060906@gentoo.org> <86y5lml15i.fsf_-_@gentoo.org> <86vcgpj8d8.fsf_-_@gmail.com> <5028BBBE.6060109@gentoo.org> <861uj8faqh.fsf_-_@gmail.com> <502C1903.1090805@gentoo.org> <86628jdyf6.fsf@gmail.com> <86y5leaxhd.fsf@gmail.com> <502DF2C5.5090209@gentoo.org> Date: Fri, 17 Aug 2012 07:56:10 -0400 X-Google-Sender-Auth: EjslFRXZ0OqQVaaQsluW_jk6Xxk Message-ID: Subject: Re: [gentoo-soc] (draft) final report for OpenRC soc project 2012 From: Rich Freeman To: gentoo-soc@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 9fa75d84-52f5-4e6d-80e4-86a828170d82 X-Archives-Hash: 75f2096335d9833b2f524a9a7b75226a On Fri, Aug 17, 2012 at 3:29 AM, Luca Barbato wrote: > On 8/17/12 7:39 AM, heroxbd@gmail.com wrote: >> Thanks a lot for the comment. I agree. Nobody cares about the tiny (not >> tested) booting up time gain with rc_parallel. > > It can be not so tiny, surely busybox+openrc gives a better gain in many > cases. > I suspect that it will depend greatly on what services you're running, and what order they happen to start in, and what you care about. In theory slamming the kernel with a ton of processes will allow it to manage its queues better with a fuller understanding of demand. systemd can potentially short-cut this a bit further since it can consider a dependency resolved if nothing more than a socket is created, which is a clever trick (I have no idea how well it works out in practice, though I have used a .socket service once and that worked out fine (with the caveat that the first connection fails)). Where I saw the bigger performance difference between openrc and systemd was in shutdown. Systemd shuts down REALLY fast, and I've noticed it tends to actually kill ssh sessions rather than leaving them unresponsive (plus ssh dies even faster so that makes it seem subjectively faster - but the difference in full shutdown is still real). Obviously people don't care as much about shutdown performance, but on a laptop (where supposedly event-driven inits should shine) I know that waiting for a full shutdown before packing up can be painful at least in the land of Windows. Just food for thought - it seems odd that parallel startup should have any issues at all, provided that service scripts don't terminate until the service is functional and all dependencies are specified. If either of those aren't true then you'll have race conditions. Rich