OpenSolaris

Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » OpenSolaris » arc

Thread: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 6 - Last Post: Mar 26, 2009 7:24 AM by: sntzutch
Guest
Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 20, 2009 3:00 AM

  Click to reply to this thread Reply



casper

Posts: 3,398
From:

Registered: 3/9/05
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 20, 2009 3:00 AM   in response to: Guest

  Click to reply to this thread Reply


This case is now open.

Fasttrack for turbo-charging SVr4 package install.

Release binding: patch/micro

Our customers using Solaris 10 have several problems:

- installing patches is slow
- liveupgrade is slow
- upgrade is slow
- liveupgrade with zones is even slower.
- installing zones is slow

Much of this is caused by the contents database /var/sadm/install/contents.
Most of the procedures listed above cause around 50-150GB of I/O
to the contents file.

Earlier attempts to get rid of the file didn't pan out. This project
proposes to keep the contents file but delay writing it.
The contents file is managed by a daemon. Package commands no
longer manipulate the contents file themselves, they call the daemon.

The pkgserv daemon stores all modifications in a logfile
(/var/sadm/install/pkglog). The "virtual contents file" is
the on-disk "contents" file and the on-disk "pkglog" file.

The daemon will lock out older versions of the package commands by grabbing
the contents lock file. (Older package commands can run again after the
daemon has exited)

The fasttrack adds the following commands/subcommands:

/usr/sadm/install/bin/pkgserv
- Consolidation private
- invoked automatically by the pkgcmds.

/usr/bin/pkgadm sync [-R root] [-q]
Writes the contents file and rolls the contents log file.
Optionally forces the contents file server to quit [-q].

- invoked automatically by the pkgcmds,
lu commands (such as luumount), install, upgrade,
liveupgrade, zoneadm install

/var/svc/manifest/system/pkgserv.xml
- defines svc:/system/pkgserv:default
- runs "pkgadm sync -q" at boot and shutdown time.
- write the contents file if needed, picks up the pieces
if pkgserv is killed, makes sure the pkgserv exits.

The new implementation uses at most as much memory (both real and reserved)
as the current implementation, but typically less.

Each zone will run its own pkgserv.

The daemon will automatically flush the contents file and it will
shut down. (By default, the contents file is written within minutes after
the last package commands exits)

The performance change is considerable:

install 25-50% (1.5-2 as fast)
upgrade 50-75% (2 - 4 times faster)
liveupgrade 50-75%
(w/ or w/o zones) (higher gain with more zones)
zone install 50-75%

Security: the daemon verifies the caller's identity using door_ucred().
Users which cannot modify the contents database will run their own read-only
version of the daemon.

It is possible to back out the new pkgcmds; the contents file stays as before,
and after the daemon is stopped, the older package commands can be reinstalled.
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc at opensolaris dot org


Garrett D'Amore
gdamore@sun.com
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 20, 2009 8:28 AM   in response to: casper

  Click to reply to this thread Reply

+1.

-- Garrett

Casper.***@Sun.COM wrote:
> This case is now open.
>
> Fasttrack for turbo-charging SVr4 package install.
>
> Release binding: patch/micro
>
> Our customers using Solaris 10 have several problems:
>
> - installing patches is slow
> - liveupgrade is slow
> - upgrade is slow
> - liveupgrade with zones is even slower.
> - installing zones is slow
>
> Much of this is caused by the contents database /var/sadm/install/contents.
> Most of the procedures listed above cause around 50-150GB of I/O
> to the contents file.
>
> Earlier attempts to get rid of the file didn't pan out. This project
> proposes to keep the contents file but delay writing it.
> The contents file is managed by a daemon. Package commands no
> longer manipulate the contents file themselves, they call the daemon.
>
> The pkgserv daemon stores all modifications in a logfile
> (/var/sadm/install/pkglog). The "virtual contents file" is
> the on-disk "contents" file and the on-disk "pkglog" file.
>
> The daemon will lock out older versions of the package commands by grabbing
> the contents lock file. (Older package commands can run again after the
> daemon has exited)
>
> The fasttrack adds the following commands/subcommands:
>
> /usr/sadm/install/bin/pkgserv
> - Consolidation private
> - invoked automatically by the pkgcmds.
>
> /usr/bin/pkgadm sync [-R root] [-q]
> Writes the contents file and rolls the contents log file.
> Optionally forces the contents file server to quit [-q].
>
> - invoked automatically by the pkgcmds,
> lu commands (such as luumount), install, upgrade,
> liveupgrade, zoneadm install
>
> /var/svc/manifest/system/pkgserv.xml
> - defines svc:/system/pkgserv:default
> - runs "pkgadm sync -q" at boot and shutdown time.
> - write the contents file if needed, picks up the pieces
> if pkgserv is killed, makes sure the pkgserv exits.
>
> The new implementation uses at most as much memory (both real and reserved)
> as the current implementation, but typically less.
>
> Each zone will run its own pkgserv.
>
> The daemon will automatically flush the contents file and it will
> shut down. (By default, the contents file is written within minutes after
> the last package commands exits)
>
> The performance change is considerable:
>
> install 25-50% (1.5-2 as fast)
> upgrade 50-75% (2 - 4 times faster)
> liveupgrade 50-75%
> (w/ or w/o zones) (higher gain with more zones)
> zone install 50-75%
>
> Security: the daemon verifies the caller's identity using door_ucred().
> Users which cannot modify the contents database will run their own read-only
> version of the daemon.
>
> It is possible to back out the new pkgcmds; the contents file stays as before,
> and after the daemon is stopped, the older package commands can be reinstalled.
>

_______________________________________________
opensolaris-arc mailing list
opensolaris-arc at opensolaris dot org


Gary Winiger
gww@eng.sun.com
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 20, 2009 8:09 AM   in response to: Guest

  Click to reply to this thread Reply

> This case is now open.

+1 in the open as well as closed.

Gary..
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc at opensolaris dot org


Guest
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 25, 2009 5:23 PM   in response to: Guest

  Click to reply to this thread Reply



casper

Posts: 3,398
From:

Registered: 3/9/05
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 25, 2009 5:23 PM   in response to: Guest

  Click to reply to this thread Reply


This case was approved at PSARC today.

Casper
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc at opensolaris dot org


sntzutch

Posts: 225
From: US

Registered: 10/13/06
Re: Fasttrack for turbo-charging SVr4 package install. [PSARC/2009/173 FastTrack timeout 03/18/2009]
Posted: Mar 26, 2009 7:24 AM   in response to: casper
To: OpenSolaris » arc
  Click to reply to this thread Reply

>
> This case was approved at PSARC today.

This is really great news.




Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2005 Sun Microsystems, Inc.