From: Peter Tribble <peter.tribble@gmail.com>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] How much OpenIndiana is lagging behind Linux in live usb technology?
Date: Tue, 30 Jul 2024 18:06:01 +0100 [thread overview]
Message-ID: <CAEgYsbFnZHJ5Eajew-MVw6DZOyT8hS0+iZ48rcqy6ersvLw=8g@mail.gmail.com> (raw)
In-Reply-To: <17222940390.7FCBa.49150@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
On Tue, Jul 30, 2024 at 12:00 AM nsgnkhibdk2cls0f via illumos-discuss <
discuss@lists.illumos.org> wrote:
> Thank you for clarification. But the overall experience with OpenIndiana
> live usb is still very bad. You should have a look at it and do something
> to improve the performance.
>
Historically, OpenSolaris/OpenIndiana/Solaris, based on the Caiman
installer, have
typically taken about twice as long as Ubuntu (which is probably a fair
comparison
out of the available Linux distros). I did some comparisons back in
OpenSolaris, and
I don't know whether there's been significant change in that ratio.
Certainly the recent
Debian installs I've done have been horribly slow.
While OmniOS and Tribblix are very very much quicker, I'm not entirely sure
how much
of that work translates directly to OpenIndiana - with different targets in
mind we can
optimize in very different directions, and both those distros wrote
something from scratch.
A couple of the things I have in my old notes last time I looked at this (I
haven't
done a regular OpenIndiana install for some years now):
1. As the live environment is absolutely static, certain things could be
precalculated
ahead of time. I think it has to calculate the lists of files to transfer,
which seems
wasteful to do each time.
2. One useful trick I do in Tribblix, again based on the notion that you
know precisely
what the install environment looks like, is to pregenerate the full SMF
respository
(by doing a test boot and saving off the repository.db. it's going to be
the same every
time) so as to avoid waiting for SMF import at first boot, which can save a
bit [especially
in some virtualized environments where manifest import seems to run
abnormally slowly].
But one of the snags is that there isn't a great deal of understanding of
the live
boot and installer internals. Being a good perl programmer many decades ago
gave me Laziness, Impatience, and Hubris, and after spending a few minutes
trying to work out what Caiman was doing I decided it was too complicated
for me so I wrote all the tools for Tribblix from scratch in a fraction of
the time.
--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
[-- Attachment #2: Type: text/html, Size: 3063 bytes --]
next prev parent reply other threads:[~2024-07-30 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 22:48 nsgnkhibdk2cls0f
2024-07-29 22:52 ` nsgnkhibdk2cls0f
2024-07-29 22:55 ` [discuss] " Toomas Soome
2024-07-29 23:00 ` nsgnkhibdk2cls0f
2024-07-29 23:55 ` Volker A. Brandt
2024-07-30 1:16 ` nsgnkhibdk2cls0f
2024-07-30 1:30 ` nsgnkhibdk2cls0f
2024-07-30 1:33 ` Goetz T. Fischer
2024-07-30 1:35 ` nsgnkhibdk2cls0f
2024-07-30 1:42 ` nsgnkhibdk2cls0f
2024-07-30 17:06 ` Peter Tribble [this message]
2024-07-30 17:17 ` Aw: " Ignacio Soriano Hernandez
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='CAEgYsbFnZHJ5Eajew-MVw6DZOyT8hS0+iZ48rcqy6ersvLw=8g@mail.gmail.com' \
--to=peter.tribble@gmail.com \
--cc=discuss@lists.illumos.org \
/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).