Native 64 Bit:
What does it take to see performance increases?

We have seen the advent of 64-Bit processors. Operating systems followed, but most applications, still written for 32-Bit systems, ran on the hardware platforms in 32-Bit compatibility mode only. What is really needed to get the performance that is the promise of 64-Bit computing?

All On the Same Page
Ok, we often have meetings with each other in our places of business to make sure we are all on the same page. It may be an overused clich, but with 64-Bit computing, that is exactly what you need. The playing field must be level. The requirements are few:

1. PC with 64-Bit Processor

2. Operating system designed for 64-Bit Processors

3. Applications designed to run on 64-Bit Processors with a 64 Bit operating system

I know this may seem simple, but it many ways it is not. The promise of speed and performance can only happen when applications running in Native 64-Bit mode are loaded on the required hardware / operating system platform. Anything less can spell disaster!

Disasterseriously?
Yes, in a manner of speaking. When the first of the 64-Bit systems (hardware and operating systems) were released, they were primarily used for servers. After that, those systems began to sneak into the high-end workstation market. The problem is that the applications were simply not there. Most application vendors were still developing their applications for the 32-Bit environment. The end result was you had this high-powered machine and operating system that was relegated to running a translator to allow the 32-Bit applications to run in a 32-Bit memory space, sort of like a virtual machine. As anyone will tell you, you lose speed with translations. Todays application choices now include 64-Bit versions, and native versions at that. With that native support, application vendors are now locking their 32-Bit versions so they will no longer be allowed to run on a 64-Bit system using some sort of translation. This may be apparent when you try to run the application or savvy developers may actually prevent the install altogether if the hardware and operating system does not work (what a concept!) Like my Dad always said, the right tool for the right job.

Where do I start and is now the time to make the move?
In todays computing world, just as it has been for years, being on the leading edge of technology is a good thing. Being on the bleeding edge is not a good thing. This is because bleeding edge refers to technology that is so new, the end user may be at risk of technology that is not stable, may cost productivity and, in most cases, is much more expensive than the tried-and-true technology of the day. The tipping point has almost arrived for 64-Bit hardware, operating systems and applications. To decide the time is right for you, you need to weigh the facts:

1. Faster processors

2. More memory support

3. Higher hardware costs

4. Application availability

For the person who accesses email, the internet and uses word processing and other applications, the time for adoption may still be way too early. On the other hand, if you have engineers who need the extra power of computing, faster rendering and analysis that 64 Bit can offer and their application of choice is now available for the 64-Bit world, now may be an excellent time to make the move. For high-end workstations, their users and the applications they require, the tipping point means that availability is more widespread.

How can I get more information on this subject?
Ask us. Our sales professionals are always ready to assist you with solutions that help make you more productive. Often, we will have additional suggestions about new solutions or emerging technologies before you take the plunge! If you have questions or comments about this article, contact me (JohnBoline@hagerman.com).
 

All product names / logos, company names / logos are copyrights of their respective holders. John Boline is an MCSE, CNE, USE and a member of the Network Professional Association. The content herein is often based on late-breaking events. Much of the material is based on information from sources that are believed to be reliable. Hagerman & Company, Inc. disclaims all warranties as to the ultimate accuracy or completeness of the information. Hagerman & Company, Inc. and its employees shall have no liability for errors, omissions or inadequacies in the information contained within this article or for any interpretations thereof. The recommendations, positions and best practice policies outlined herein represent Hagerman & Company, Inc. initial analysis and therefore are subject to change as further information which may have bearing on these positions is made available. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice. Entire contents 2007 Hagerman & Company, Inc. All rights reserved. Reproduction of this publication in any form without prior written permission is forbidden.