Void Linux discussion
 help / color / mirror / Atom feed
From: bougyman <boug...@rubyists.com>
To: voidlinux@googlegroups.com
Cc: walach.o...@gmail.com
Subject: Re: What's a complete "just works" distro?
Date: Tue, 7 Apr 2015 13:38:13 -0700 (PDT)	[thread overview]
Message-ID: <93c6b135-ad7d-4c7f-b462-43c0e2a934f9@googlegroups.com> (raw)
In-Reply-To: <3b8920b2-49e1-4be5-a8d1-949ae4f25657@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 2111 bytes --]

I have some benchmarks on this from a few years ago and runit was 
definitely speedier than systemd boots (on archlinux) then. From the DW 
reviewers comments it seems this is still the case, at least
in the case of runit-void's speed. This mostly affects boot time, but the 
low overhead of a static runit vs the many binaries of system plus its own 
heft could make a difference on strained-for-resources machines, I suppose, 
but
likely not on some A/V production rig.

bougyman

On Sunday, March 22, 2015 at 10:30:26 PM UTC-5, Logen Kain wrote:
>
> >>TBH, I never understood this argument.  All Linux distros compile 
> >>roughly the same sources... why would one be faster than another?
>
> I think runit has a lot to do with it.  Even compared to Arch which I've 
> also streamlined... Had I never saw Void before I would think that the 
> computer must have an SSD in it.
>
> It's some times quicker for me to "git clone" and compile packages on void 
> than it is to download something from apt.  Seriously, Ubuntu competes with 
> windows now for slow updating.
>
> Before using Void, I have never seen firefox open this fast, again I used 
> to be a fan of Arch Linux and openbox combo.
>
> On an R61 Laptop I used to use, windows 7 (came with it refurb) ran pretty 
> ok. I didn't use it more than a day before I started installing Linux 
> distros.
> All Ubuntu derived distros were horribly slow to install, boot, and open 
> aplications.
> Arch was pretty fast, but nothing compared to void.  Sabayon felt a little 
> quicker than arch.
>
> I typically used MATE at the time, or KDE.
>
> Thinking of KDE.  When I install and start up KDE for the first time, it 
> has always been stupid slow.  Decent boot up times after the first boot.
>
> With Void, it was way faster than I've ever seen it boot.  Even for a 
> first boot.
>
> I don't know what kind of black magic Void weilds, but if it wasn't for 
> Void, I'd agree with the idea that all distros are pretty much the same.
>
>
> Perhaps I wouldn't notice much of a difference if I used SSD.
>

[-- Attachment #1.2: Type: text/html, Size: 2318 bytes --]

  reply	other threads:[~2015-04-07 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22  0:17 Logen Kain
2015-03-22  7:58 ` Juan RP
2015-03-22 14:07 ` Christian Neukirchen
2015-03-23  3:30   ` Logen Kain
2015-04-07 20:38     ` bougyman [this message]
2015-03-22 17:29 ` Stefan Mühlinghaus
2015-03-23  3:38   ` Logen Kain
2015-03-22 21:46 ` JD Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93c6b135-ad7d-4c7f-b462-43c0e2a934f9@googlegroups.com \
    --to="boug..."@rubyists.com \
    --cc="walach.o..."@gmail.com \
    --cc=voidlinux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).