To 64 or Not to 64, That Was the Question

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. 
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.








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago