Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: How to speed up zypper and YAST2 when installing appz?

  1. #11
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,564
    Blog Entries
    38

    Default Re: How to speed up zypper and YAST2 when installing appz?

    Quote Originally Posted by robin_listas View Post
    Failure: package b.rpm fails to download mid-ways, while a.rpm is being
    installed.
    That can be a problem.

    And its more likely to happen if rpms are are installed immediately after downloading than if they are all downloaded first and only then installed.

    Quote Originally Posted by robin_listas View Post
    > If that indeed is the way apt-get works, then I certainly would want no
    > part of it.

    I would, very much >:-)
    Thats the beauty of Linux, we both have the choice to tune it the way we prefer.

  2. #12
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: How to speed up zypper and YAST2 when installing appz?

    On 02/17/2011 02:03 AM, Carlos E. R. wrote:
    > Simple. A double is a comment, a single is a variable or setting commented
    > out, but which you can activate by uncommenting it out.


    thanks, i had guessed that an removed both ## for those i wanted active..

    but, that does prompts another question:

    since there were zero settings uncommented, that must mean that all of
    the ones with a single # are the default *and* carried somewhere else
    as active (uncommented) right?

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  3. #13
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: How to speed up zypper and YAST2 when installing appz?

    On 2011-02-17 10:26, DenverD wrote:
    > On 02/17/2011 02:03 AM, Carlos E. R. wrote:
    >> Simple. A double is a comment, a single is a variable or setting commented
    >> out, but which you can activate by uncommenting it out.

    >
    > thanks, i had guessed that an removed both ## for those i wanted active..


    A double "##" indicates that you should not uncomment that line: it is a
    real comment, not a deactivated setting.

    > but, that does prompts another question:
    >
    > since there were zero settings uncommented, that must mean that all of
    > the ones with a single # are the default *and* carried somewhere else
    > as active (uncommented) right?


    It is nice of programmers to provide us with a configuration file with all
    the default settings written, but commented out. It behaves as if the file
    did not exist, but shows us what the file would look like, and it makes for
    easy changes.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  4. #14
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: How to speed up zypper and YAST2 when installing appz?

    On 2011-02-17 10:36, oldcpu wrote:
    >
    > robin_listas;2290989 Wrote:
    >>
    >> Failure: package b.rpm fails to download mid-ways, while a.rpm is being
    >> installed.

    >
    > That can be a problem.
    >
    > And its more likely to happen if rpms are are installed immediately
    > after downloading than if they are all downloaded first and only then
    > installed.


    The default zypper behaviour is to download a.rpm, then install a.rpm, then
    download b.rpm, then install b.rpm, etc. In that situation, moving the
    download to a different thread is of no consequence, except speed.

    If you select to download all first, then it is not possible to parallelize.

    If you select to download and install in batches, it could download the
    next batch while the previous batch is being installed. A failure to
    install a part of the batch is then no different than what we have now (the
    batch is fully downloaded at that time).

    >
    > robin_listas;2290989 Wrote:
    >>> If that indeed is the way apt-get works, then I certainly would want

    >> no
    >>> part of it.

    >>
    >> I would, very much >:-)
    >>

    > Thats the beauty of Linux, we both have the choice to tune it the way
    > we prefer.


    /IF/ zypper was threaded, which it is not.


    What I intend to show is that parallel download/install is as safe as
    sequential download/install. The exception would be if the download program
    itself, or its libraries, is changed while it is running. Or perhaps not,
    because unix/linux does not delete an "in-use" file.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  5. #15
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,564
    Blog Entries
    38

    Default Re: How to speed up zypper and YAST2 when installing appz?

    Quote Originally Posted by robin_listas View Post
    If you select to download all first, then it is not possible to parallelize.
    True.

    Quote Originally Posted by robin_listas View Post
    If you select to download and install in batches, it could download the
    next batch while the previous batch is being installed. A failure to
    install a part of the batch is then no different than what we have now (the
    batch is fully downloaded at that time).
    There is a difference. The difference is in the probability of occurence. In the case of downloading one, installing, downloading another, installing, a failure in the internet connection will cause an interuption in the installation at potentially a bad location. But if one needs to download all rpms first and ONLY after a successful download start the install, then the internet reliability is no longer part of the equation.

    Quote Originally Posted by robin_listas View Post
    What I intend to show is that parallel download/install is as safe as sequential download/install. The exception would be if the download program
    itself, or its libraries, is changed while it is running. Or perhaps not, because unix/linux does not delete an "in-use" file.
    Well, we differ in our views here. I don't see Internet reliability as being guaranteed, and far too often have I seen in a large download an internet hiccup causing a problem.

    But as noted, the beauty of Linux is we both can tune this the way we like. The flexibility is there for each of us to set this up the way that we think works best for us and not have the views of the other (with whom we don't agree) imposed.

  6. #16
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: How to speed up zypper and YAST2 when installing appz?

    On 02/17/2011 12:03 PM, Carlos E. R. wrote:
    >> thanks, i had guessed that an removed both ## for those i wanted active..

    >
    > A double "##" indicates that you should not uncomment that line: it is a
    > real comment, not a deactivated setting.


    of course, i wasn't thinking when i wrote here...yes i didn't try to
    make a comment (with ##) an option !!

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  7. #17
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: How to speed up zypper and YAST2 when installing appz?

    On 2011-02-17 13:06, oldcpu wrote:

    > robin_listas;2291207 Wrote:
    >> If you select to download and install in batches, it could download the
    >> next batch while the previous batch is being installed. A failure to
    >> install a part of the batch is then no different than what we have now
    >> (the batch is fully downloaded at that time).

    >
    > There is a difference. The difference is in the probability of
    > occurence. In the case of downloading one, installing, downloading
    > another, installing, a failure in the internet connection will cause an
    > interuption in the installation at potentially a bad location.


    Yes, that is what zypper does now by default. This is what we have, and it
    is bad.

    What I say that you could have this option enabled:

    ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split
    ## the transaction into heaps, where at the end of
    ## each heap a consistent system state is reached.

    The key is that it first downloads all the packages conforming a batch,
    then installs all of those packages, reaching a consistent system state.
    That is what zypper does currently if that setting is active. The
    improvement would be that at the same time it is installing the first batch
    it could start downloading the second batch. These two processes are
    independent, the failure of one does not affect the other.

    It is a technical matter, not a matter of opinion ;-)
    The problem is that you are not understanding what I try to explain.


    > But if
    > one needs to download all rpms first and ONLY after a successful
    > download start the install, then the internet reliability is no longer
    > part of the equation.


    Obviously. But you have to select that behaviour, it is not the default.
    The default is:


    ## DownloadAsNeeded Alternating download and install. Packages are
    ## cached just to avid CD/DVD hopping. This is the
    ## traditional behaviour.


    > robin_listas;2291207 Wrote:
    >> What I intend to show is that parallel download/install is as safe as
    >> sequential download/install. The exception would be if the download
    >> program
    >> itself, or its libraries, is changed while it is running. Or perhaps
    >> not, because unix/linux does not delete an "in-use" file.

    >
    > Well, we differ in our views here. I don't see Internet reliability as
    > being guaranteed, and far too often have I seen in a large download an
    > internet hiccup causing a problem.


    It is not guaranteed. I never said that.

    What I say is that you can get the same reliability with parallelization or
    without.


    > But as noted, the beauty of Linux is we both can tune this the way we
    > like. The flexibility is there for each of us to set this up the way
    > that we think works best for us and not have the views of the other
    > (with whom we don't agree) imposed.


    Not yet, we don't have the parallel behaviour option.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •