Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-06-2010, 07:54 PM
|
#1
|
Member
Registered: Mar 2009
Distribution: Slackware 13.0
Posts: 60
Rep:
|
For the computer with Intel i5 2.26 Ghz and 3 GB RAM
I heard, as long as the memory is less than 4GB, it does not matter if the OS is 64-bit or 32-bit....
Which type of OS would you recommend running under i5 2.26 Ghz and 3 GB of RAM? 64-bit or 32-bit?
thanks
|
|
|
02-06-2010, 08:13 PM
|
#2
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,986
|
Hi,
Actually if you use ' PAE' then access to memory greater than 3GB is possible for a 32 bit kernel. Sure you would either have to get a kernel with that enabled or compile a new kernel.
I do suggest that a 'LiveCD' from ' The LiveCD List' would allow you to test drive a distribution.

The above links and others can be found at ' Slackware-Links'. More than just SlackwareŽ links!
|
|
|
02-06-2010, 09:37 PM
|
#3
|
Member
Registered: Sep 2009
Posts: 196
Rep:
|
...
Last edited by Smartpatrol; 03-11-2010 at 10:04 PM.
|
|
|
02-06-2010, 11:33 PM
|
#4
|
Senior Member
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,339
|
32 bit because 64 bit even though it can access more memory, it uses more also.
Meaning if you have less then 4 gb ram, always use 32 bit or you will get less out of your ram.
|
|
1 members found this post helpful.
|
02-07-2010, 01:59 AM
|
#5
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,422
|
??? - explain please smeezekitty.
|
|
|
02-07-2010, 07:46 AM
|
#6
|
LQ Guru
Registered: Dec 2007
Distribution: Centos
Posts: 5,286
|
Quote:
Originally Posted by beckettisdogg
Which type of OS would you recommend running under i5 2.26 Ghz and 3 GB of RAM? 64-bit or 32-bit?
|
It probably will make only a small net difference. Probably 64bit will run a little faster. It depends on what programs you will be running, but even if you could tell us what programs you would be running, there aren't good controlled experiment data available to say which programs run how much faster or slower in 64 bit.
Quote:
Originally Posted by smeezekitty
Meaning if you have less then 4 gb ram, always use 32 bit or you will get less out of your ram.
|
The 64 bit build of a program tends to be a slightly larger binary, so it will use a little more memory for code. Pointers are twice as large in 64 bit, so depending on how heavily a program uses pointers it might use a lot more memory for that. Many 64 bit systems need a few 32 bit applications, so they often have both the 32 and 64 bit build of a shared object in ram at once, when a 32 bit system would need only one.
If you have very little ram, the above factors would be a good reason to not use 64 bit. But for most home users 3GB is a lot of ram. So the extra used by 64 bit won't have a noticeable effect.
You care whether you get more or less out of your computer, not whether you get more or less out of your ram. If you are running some program that gets a big performance boost from SSE and/or the extra registers of 64 bit mode, that extra speed would overwhelm the tiny performance loss from having slightly list caching because executing programs are slightly larger.
Last edited by johnsfine; 02-07-2010 at 07:56 AM.
|
|
|
02-07-2010, 08:17 AM
|
#7
|
Senior Member
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
|
For what it's worth, at 3GB I didn't see any significant difference 32 vs 64, or with 6GB using a 32bit/PAE kernel vs a 64 bit kernel....at least as far as basic desktop (surfing the net, watching youtube etc, playing music). Build times and things of that nature, seem to be better using a 64 bit kernel, although I have no hard data.
32 bit systems will be more compatible with more software at the present moment, but you can always use a multilib OS or if slackware is your choice use BOB'S scripts and tutorials to make your 64 system multilib.
Personally I've been running a 64 bit system since Vista came out (THAT was compatibility HELL) with no serious consequences.
|
|
|
02-07-2010, 08:58 AM
|
#8
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,986
|
Hi,
There are plenty of benchmarks to support the 64 kernel over the 32 bit kernel.
The point that everyone should look at is the number of 32 bit machines overall as compared to the number of 64 bit based systems in the world. That's why we will still find 32 bit applications thus the multilib capability for a 64 bit kernel system to use the same app. Not all developers will move to a 64 bit kernel. Some will at a point in time but most will just remain 32.
I do use Slackware with 32 & 64 bit systems. The need to provide 32 multilib on my 64 machines hasn't come up at this time. Plus I keep test benches for 32 bit work, just because the hardware is available.
Bit flipping or just plain balancing doesn't turn me on. My machines meet the needs they were designed for thus why argue the point of 64 vs 32 or even 'PAE' on 32 to gain that extra memory address-ability.

|
|
|
All times are GMT -5. The time now is 08:11 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|