Bug 194472

We should really deal with those performance issues for 10.2. What you described is all conected to the packager. People are working quite hard on this atm ;)
I am reassigning this report to the maintainer.

Duncan is already working on increasing performance.

Created attachment 101279 [details]
.jpg screen shot showing both CPU near max on execution of online update

Online Update Already consuming near MAX on both CPU's to perform its task - see screen shot.
If system usage .jpg adds to current bug report
Should validate further this bug report.

Why cant we go back to suse watcher - version 10.0 appeared to have no abundance of problems

P.S Should status be "assigned" if being working on

For certain operations, yast2 is really great because it is quite complete, and the installer is the best installer of all the distros I have seen.

However, for doing updates, which are confusingly called "patches" in yast, it is a nightmare from two standpoints.  1. Your "updates" repository frequently gets into a condition where the dependencies of the updates cannot be met. This is currently the case for updates to yast and zmd.  With yast, it is very difficult to exclude the troublesome updates.  Perhaps this problem occurs because I do not permit automatic updates, which means if I wait a few weeks, you may have updates to updates.  In any case, your update repository is not complete and consistent.
2. As is the subject of this bug report, your yast package update/install process is too slow by several orders of magnitude, which means it is totally unusable in a large shop of more than 1 or 2 computers.  I recently switched to using yumex and this has pretty much resolved this problem as well as given me a relatively simple way of getting around point one.  I've also turned off the zmd daemon as it periodically wakes up and eats all my cpu time preventing me from working -- this is particularly serious on my 700MH laptop.
3. The version of yumex that you distribute is *way* out of date.

I'm not trying to give you a hard time, but hope this will help you understand that the default yast package updater is a big handycap for professional shops.

One final thing.  Your method of entering repositories via a GUI is nice for dummies, but is another nightmare for sys admins.  I have yet to find a simple ASCI file where I can edit the repositories -- I hope you have not defined this in the traditional Windows way using binary files.  On the other hand, once I took the trouble to set up a yum repository using my trusty editor it, unlike yast, it is trivial to bring it up on another machine -- I just copy the files in /etc/yum.d to the new machine -- presto I am up and running.  Yumex sometimes seems slow, but it is 10 - 100 times faster than yast.

On my laptop, 1.5 year old, it takes 34 minutes after booting before I can start to work with a reasonable performance. This is unacceptable.

Please, check the performance with 10.2. For 10.1, the work that was feasible is already available as online update.

Concerning comment #6: I will load 10.2 this weekend and test it on my 400MHz machine, providing the CD ISOs are available.

Concerning comment #5 (yast on a laptop): my solution to the same problem was to disable novell-zmd either with chkconfig or using daemon configuration. For updates, either re-enable it, or switch to using yumex as I did.

RE: comment 4. The day Linux will NOT need file editing and massive usage of the command line will be the day we produce a product world standard.

The ratios of admins to users is very low. The name of the game is to provide a GUI interface that not only a select few admins can use - but the world.

Once there was DOS - it died because of a complex???? command line and lives the giant GUI interface which Linux is ever to succeed will come to.

There have been major changes to YOU as of today..will close as remind and monitor, RAM consumption seems lower on stats.

This is not to say we need to be mindful of the hours taken to perform updates.

For those users with a large number of PC's I strongly suggest update via NFS.

I also agree that the ZMD ported from Novell Netware desktop is another problem more accurately described in another bug report. ( Sorry guys just had to rebuild my system and don't have the number.

Created attachment 104789 [details]
Screen capture when mirror was busty in the middle of the day from software management

Recent changes to YOU version now 2.13.43.2-0.2 are still unacceptible see error attached and YAST files as requested. Note log files will not contain this snapshot error. This error is faithfully re-producable IFG the selected mirror is either BUSY or not apparent.

YAST also takes an increadibly long time to load - over 4 mins in a P4 HT 3.2 1.5GIG 

Please do NOT pass these frustations on both our side to version 10.02

Re-Opened after testing new version of YOU as indicated and YAST files as requested

I loaded SuSE 10.2 beta 2 last weekend on my 400MHz 256MB Pentium II, and it seems to me that there is a big improvement in the speed of the configuration of packages to be loaded. The longest wait time was 1 minute, and in most cases (not all) when I worked with the hardware or other configuration info, it did not go through the long wait for the packages.

I'm not sure if there is any additional testing I can do since, unless I am mistaken, there are no repositories for 10.2.

Kem on your assessment I am happy to close this bug.

I'm just loading SuSE 10.2 RC1 on my laptop, and wanted to report that the package selection is *very* fast compared to 10.1.  If the yast package selection on a running 10.2 is as fast, I will be very happy.

By the way, the Christmas graphics on the start up screen when booting the 10.2 RC1 boot CD are really slick. :-)

In version 2.13.43.2-02 of YOU the CPU utilisation is perfectly acceptable suggest resolved fixed see screen shot.

Created attachment 108238 [details]
.jpg showing CPU max utilisation on online update

According to comment #14, resolving as fixed.