Skip to main content

Linux Magazine: Having Yum for Breakfast

Found that article from Linux Magazine titled Having Yum for Breakfast via Distrowatch. According to the test apt-deb easily beats yum. Any comments about result and factors that affect it? From what I understand, apt-deb is static by nature unlike yum (dynamic) which could probably explain faster transaction.

Update: Added author's blog related to the article.

Comments

Jef Spaleta said…
See if you can get the exact step-by-step methodology used in creating the benchmarks.

better yet see if you can get the full log of the screen session used to do create the data for the benchmarks.

There could be a flaw in the methodology that biases towards apt operation. Can't know if it was a fair test unless the specifics of how to run the test are made available for review.


-jef
Anonymous said…
I think that article is some FUD on yum. In the comments the author (assuming that it is the writer) seems to point out that, these tests where not done on a network as noted here (the emphasis is mine)
"That’s true, but it’s rather hard to test, especially when connection speeds come into it and finding packages the same size. I think it’s safe to say that you’ll be downloading less by using the deltas than you would on Debian.

For these tests, all packages were pre-downloaded so bypass the network download issue."

I find that odd since, based on there functions, network downloads are what they do. Even with the localinstall flag, fetching from the internet is what they are designed for... so this review seem to be designed to do something that yum nor apt happened to be designed for?

I don't know, that seems odd... Maybe I am wrong?
Duv
Jef Spaleta said…
duvworld

You are wrong, in a way. Network activity across the external internet can be subject to all sorts of different factors outside of your control. Such network activity would distort the timing benchmarks greatly.

Its actually far more scientific if you work from local caches of the repository metadata and the packages to avoid any external network activity during the benchmark tests. These tools do all their dep resolution transactions from local data stores regadless. Excluding the variability of network access is actually the most appropriate thing to do if your goal is to test transaction speed.

That being said, pulling packages and/or repository level metadata across the network has an objective cost in terms of user interaction perception, that is worth talking about, if you can adequately separate that out from other operations.

In fact my biggest concern is that the benchmark author did not adequately segregate network activity for repository metadata when doing the test.
To make sense of the benchmarks I need details of the methodology used to run the tests, so I can reproduce the tests for myself.

-jef
Jef: Good catch about the log. To answer the first paragraph, I cannot because of the lack of information of packages used for the test.

Also the way both yum and apt differ is due to the fact yum is designer for smooth transaction like for example: yum update is equivalent ot apt-get dist && apt-get update (I can't remember as I haven't used it for a while).



duvword: The author and writer is the same. He used to build Kororaa, a Gentoo based distribution, and mostly manually update package. I am updating the blog to add his blog so issues can be discussed.

Popular posts from this blog

Drawing hair with Inkscape

My very first online tutorial is an adaption from Chris Design Drawing Hairs article using both Path and Path Editor tools which requires Inkscape 0.47 or newer. Start-up Inkscape application which should open a new blank page and set the document into landscape.  Create a path Select the bezier tool or press either Shift+F6 or B on the keyboard. Draw a line to approximately 800px or more. You can also use rectangle tool ( R or F4 as shortcut key) as a thin line illustrated in grey. While the line is selected, convert into path from the menu Path -> Stroke to Path or press Ctrl+Alt+C on the keyboard. For the rectangle, Path -> Object to Path or Ctrl+Shift+C . The result will show grey diamonds on each corner. Create a pattern On the menu, Extensions -> Modify Paths -> Add Nodes . Set the Max Segments Length to 5px. On the menu Extension -> Modify Paths -> Jitter Nodes . Leave the default settings and apply effects.

HP, Linux and ACPI

 Majority of HP hardware running on Linux and even Microsoft reported an issue related to a non-standard compliant ACPI. Notable message below repeats at least three times on the boot: 4.876549] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190215/dsopcode-198)  [ 4.876555] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529)  [ 4.876562] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529) The bug is a known for years from which Linux kernel team are unable to fix without the help of vendor i.e. HP. Here is a compilation of reports: BIOS error: The BIOS in this system is not fully ACPI compliant. ACPI BIOS ERROR (blue screen) on startup   ACPI bad works with Linux    The good news is some errors seems harmless. Unfortunately, such errors displayed the quirks approach used by

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example. Extracting the tarball contains the following: amdgpu-install amdgpu-pro-install symlink to amdgpu doc folder repodata folder RPMS folder containing rpm package Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line: ./amdgpu-install -y --opencl=pal --headless Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST. No match for argument: amdgpu Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial. Due to its design, Gnome