Language Selection

English French German Italian Portuguese Spanish

To 64 or Not to 64, That Was the Question

Filed under
Reviews

With my nice new motherboard & cpu, I've been quite anxious to test some of my new-found powers. My first thought after the hardware installation was: Gentoo 64-bit! By way of testing, I installed the 64-bit version of SuSE 10.1 rc1 yesterday and had planned on writing this wonderfully informative comparison article of it and the 32-bit version. I was expecting the 64-bit to smoke 32 and had even made preliminary reads into installing the 64-bit version of Gentoo. Since this was my first foray into the world of 64-bit, I expected to be lost and confused. Well, the former may not have come to fruition, but the latter certainly did.

The install went fine. No errors or problems were had. It went as smoothly as the 32-bit the day before. I chose all the same options, packages, etc as the other system and again, I was expecting the install to be quite faster.

Now here's my first mistake for the planned article: I didn't time the 32-bit install, so saying the 64-bit seemed faster is about as precise as I can be. In total from soup to nuts it took right at an hour. The best I can estimate for the 32-bit is little over an hour just for the packages. As much as I love all my readers, I just couldn't talk myself into a reinstall of the 32-bit system just to time it. So, no legitimate points in this category can be given to either system.

        

Ask any expert in the technology field and they'll tell you boot times and application open times are not an accurate means of testing the speed of an operating system. But you know, to the average Joe, this is exactly was speed means to us. So, I had big plans of putting this great comparison chart together that we could all ooo and aah over. I thought another great test would be compile times of a notoriously long build. As you can see from the chart below, our "notoriously long build" failed on the 64-bit and as a result I just skipped it on the 32-bit. But quite frankly, the other speed increases of the 64-bit applications are quite unimpressive. With the failed compile taking the wind outta my sails, this article idea almost withered on the vine. In fact, I'd not even be publishing this at all, even as a blog, if not for the really slow news day and my needing something to post. Big Grin

For the boot test, this was timed with a stopwatch from the moment of depressing the enter key on their entries in lilo 'til the KDE desktop was fully up and ready. Autologin was enabled for the default user. Fully up and ready meant all informative "pop-ups" had disappeared and "busy cursors" had stopped. I used the same X driver and the same options enabled for it as well as kde, and the only app to 'restore' was a two-tabbed konsole on each of the same approximate size. Suse 64 had been booted a few times prior to the test to allow for all of its pre-configuring and such to complete and the tested applications had been started and closed a few times. For the test, the opening of apps were the first for them after a fresh reboot.



32-bit     64-bit
Boot 85 secs 80 secs
Firefox blank 3 secs 3 secs
Firefox TM home 8 6
Firefox Compile failed skipped
OOowriter 6 5
Shutdown 30 27



There are two sides for every argument and there are masses of supporters for each side. But basically the 64-bit experience was a let down for me here. As I read the documentation for installing 64-bit Gentoo systems and saw references to about 20 other docs for special instructions in order to get common tools and basic apps to work, and considering the lackluster performance increase of the same binary distro and setup over it's 32-bit counterpart, I for one am not impressed with the progress of the 64-bit computing systems at this point.

In my Gentoo install I've changed my cflags for athlon64 optimizations with some supported use flags (and emerge'd -e world), am using a k8 kernel, and am rebuilding KDE --with-cflags=march=athlon64. But that's about all I'm interested in as far as Gentoo is concerned for now.

As far as other binary 64-distros? You betcha I'll be checking them out regularly.

Is the failing of one infamously stubborn package to compile enough to say the compiler don't work? Of course not. But no problems were had compiling Firefox 1.5.0.2 on my Gentoo system or my best friend's PCLOS system. As far as stability was concerned with SuSE 10.1 rc1 x86_64, there were no issues. It was as rock solid as any other SuSE install I've had over the passed year. It seemed as functional as it's counterpart with no application failure as far as I tested (which I admit was limited). If you want a binary based 64-bit distro and use only pre-compiled software for that distro, then why not. Go for it.

But am I going to build a new Gentoo 64-bit system? Nope. Maybe later.

More in Tux Machines

Q4OS 1.4.7, Orion

Another update of Q4OS 'Orion' desktop is available, version 1.4.7. A complete Trinity repository has been added to the system as the main new feature. Access to all the Trinity software were given to users by default, there is no need to add external Trinity repositories anymore. Bunch of important packages updates and security patches has been delivered as usual. Read more

Slackware Live Edition – on its way to 1.0?

Last week the second Beta of the upcoming Slackware 14.2 was released. My goal was to have a new Beta of my liveslak ready by that time, so that I could provide new ISO images to test the Slackware Beta2 on a live medium. Unfortunately, there was an attack of the flu in my team at work and things got a bit busier than usual. There was a plus side to this: some last moment bug fixes which could be applied to my scripts – the result of having more evenings available to test. Therefore the new release is not labeled “0.5.0” but “0.5.1” Read more

Leftovers: KDE

  • Cantor migrating to Phabricator: which tools our contributors must to use
    Projects and software developed by KDE community are going to migrate for a new tool to manage our code, commits, reviews, tasks, and more. This tool is Phabricator and you can visit the instance for KDE projects in this address. Since November 2015 we are migrating Cantor to Phabricator. After our first successful review code some days ago, I decided to write a post about which tools our contributors must to use while the migration process is not finished.
  • Kdenlive's sprint report
    Last week-end, Vincent and me met in Lausanne for a Kdenlive sprint. One of our goal was to merge Gurjot Singh Bhatti's GSoC work on curves for keyframes. This was more work than expected and we spent many hours trying fix the curves and make keyframes behave correctly. Not much time was left for sleep, but we still managed to get outside to make a group (!) picture in the woods above Lausanne.
  • Jekyll 3.x
    I’ve found three different types of transition issues (it is cool to look at these in a project I do not upgrade on a daily basis like Plasma and the rest of the KDE software).
  • kdev-python on Windows: try it!
    I spent the last two or three days playing around with KDE on Windows, with the aim of getting my Python language plugin for KDevelop to run there. In the end, it wasn’t that hard to get this to work — not as hard as I would have expected it to be, anyways.

Manjaro ARM launched

Hi community, wonderful news in regard of architecture expanding within Manjaro Linux. It all started with a simple post on our developers mailing list. Somebody wants to do Manjaro for ARM … Just after one month of development our first alpha release is now ready. So what is this all about? Manjaro Arm is a project aimed to bring you the simplicity and customability that is Manjaro to ARM devices. These devices are growing in numbers and can be used for any number of applications. Most famous is the Raspberry Pi series and BeagleBoard series. Read more