GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
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.
Depends on what your current system is compiled for. If it was compiled using i386 flags, yeah, 64-bit will be faster. If it was compiled with 686 flags, then probably not. The MAIN advantage you'd see with the 64-bit is being able to address and use all 4 GB of your memory, instead of only 3.5 GB (I think) of it (32-bit will see 4 GB, but only use 3.5 if I remember correctly). Of course, you could use a PAE kernel and then you'd be able to see and use all 4 GB, so that's not a HUGE issue either way (plus it's only .5 GB...so not a huge amount either).
The biggest reason to go 64-bit if your system supports it, IMO, is because going forward, some non-foss software simply will stop being available in 32-bit. Such as with Chrome already. They've decided it's simply not worth continuing to support building it for 32-bit, so they've discontinued 32-bit linux Chrome. Other software will follow suit, simply because of how high the percentage of systems that can run 64-bit is now, given that AMD hasn't made a non 64-bit processor in almost 13 years, and Intel it's been over 5, and their mainstream processors are almost 10 (atoms stayed 32-bit for a long time, that's the only thing since the core2 was released they had that was still 32-bit only). The performance difference between 32-bit and 64-bit for most software is negligible at best, and with some software, 32-bit still actually performs better. So unless you're doing massively intensive apps (video editing, audio mastering, 3d graphics), you're not losing anything staying with 32-bit for now.
Last edited by Timothy Miller; 04-05-2016 at 09:00 PM.
Has anyone who went with a 64 bit system noticed any real speed improvements ?
Hi Andy...
Maybe a little. Before the original hard drive went out in my laptop, I had Ubuntu 10.04 64 bit installed. After replacing the drive, I installed Lubuntu 32 bit to cut down the segmentation faults I was getting on a couple of the games that I liked to play. I haven't noticed a whole lot of difference. Probably the biggest difference is the browser, for some reason. Firefox seemed to load much quicker on Ubuntu then Chrome does with Lubuntu. But that may be because of something else.
Depends on what your current system is compiled for. If it was compiled using i386 flags, yeah, 64-bit will be faster. If it was compiled with 686 flags, then probably not. The MAIN advantage you'd see with the 64-bit is being able to address and use all 4 GB of your memory, instead of only 3.5 GB (I think) of it (32-bit will see 4 GB, but only use 3.5 if I remember correctly). Of course, you could use a PAE kernel and then you'd be able to see and use all 4 GB, so that's not a HUGE issue either way (plus it's only .5 GB...so not a huge amount either).
The biggest reason to go 64-bit if your system supports it, IMO, is because going forward, some non-foss software simply will stop being available in 32-bit. Such as with Chrome already. They've decided it's simply not worth continuing to support building it for 32-bit, so they've discontinued 32-bit linux Chrome. Other software will follow suit, simply because of how high the percentage of systems that can run 64-bit is now, given that AMD hasn't made a non 64-bit processor in almost 13 years, and Intel it's been over 5, and their mainstream processors are almost 10 (atoms stayed 32-bit for a long time, that's the only thing since the core2 was released they had that was still 32-bit only). The performance difference between 32-bit and 64-bit for most software is negligible at best, and with some software, 32-bit still actually performs better. So unless you're doing massively intensive apps (video editing, audio mastering, 3d graphics), you're not losing anything staying with 32-bit for now.
When running free, I usually have at least 1 Gb of free memory.
It looks like that while 64 bit has some advantages, probably 80% of users would not take advantage of it.
I dare say it's higher than 80% of users who won't actually take ADVANTAGE of it. All my systems run 64-bit, but I guarantee that I have no advantage in it, I simply prefer it.
I have 64-bit capable laptop hardware (ThinkPad T61) but choose to run 32-bit Slackware on it. In my non-scientific experience, I found no practical advantage, based on my owns needs, to choose 64-bit. I use the .smp kernel, and all RAM is recognized.
Maybe a little. Before the original hard drive went out in my laptop, I had Ubuntu 10.04 64 bit installed. After replacing the drive, I installed Lubuntu 32 bit to cut down the segmentation faults I was getting on a couple of the games that I liked to play. I haven't noticed a whole lot of difference. Probably the biggest difference is the browser, for some reason. Firefox seemed to load much quicker on Ubuntu then Chrome does with Lubuntu. But that may be because of something else.
Do you have 64 bit capable hardware?
Regards...
I have 64 bit hardware.
Seamonkey uses about 30% of my dual core CPU.
I am surprised at how much cpu browsers use especially when no downloads/uploads are occurring.
Quote:
BIBLE JOKES
from ASKTHEBIBLE.COM
Thanks everyone for your contributions to this site. Jokes have been sent in over the last year and are now included.
and YES, you can send us Bible Jokes to add to our list but certainly not Sexual or Blasphemous ones.
Which biblical character was the youngest to speak foul language?
AAAAAJob, because he cursed the day he was born.
Did you know Jesus was an American Indian?
AAAAAHis name was chief cornerstone.
Who was the fastest runner in the bible?
AAAAAAdam because he started first in the human race.
Why didn’t Cain bring God an acceptable offering?
AAAAABecause he wasn’t Abel!
How did Moses make his tea?
AAAAA"Hebrewed" it
Who is the shortest man in the Bible?
AAAAANehemiah (KneehighMiah)
A TRUTH
What is the one and only “man made” thing in heaven?
AAAAAThe scars from nails on Jesus hands and feet!
Who was the greatest financier in the Bible?
AAAAANoah. He was floating his stock while everyone else was in liquidation.
Who was the greatest female financier in the Bible?
AAAAAPharaoh's daughter. She went down to the bank of the Nile and drew out little prophet.
What kind of man was Boaz before he got married?
AAAAARuth-less.
Who was the first drug addict in the Bible?
AAAAANebuchadnezzar. He was on grass for seven years.
What did Eve ask Adam during their first argument?
AAAAA"Adam, is there another woman?"
At what time of day was Adam created?
AAAAAA little before Eve.
Did Eve never have a date with Adam?
AAAAANo, it was an apple.
Where is the first math problem mentioned in the Bible?
AAAAAIn Genesis, when God told Adam and Eve to go forth and multiply.
JOKES about NOAH
Why on Noah's ark couldn't they eat apples?
AAAAABecause they only came in pears
On the Ark, Noah probably got milk from the cows on-board. What did he get from the ducks?
AAAAAQuackers
Which animal on Noah's Ark had the highest level of intelligence?
AAAAAThe Giraffe
When was the first meat mentioned in the Bible?
AAAAA When Noah took Ham into the ark.
Why did Noah have to punish and discipline the chickens on the Ark?
AAAAA Because they were using "fowl" language.
How many people went on board the Ark before Noah?
AAAAA Three, because it says "... and Noah went forth"
JOKES LOT'S WIFE
Lot's last words to his wife?
AAAAA...Honey, is someone following
OR
Why was a woman in the Bible turned into a pillar of salt?
AAAAABecause she was dissatisfied with her Lot.
GENERAL BIBLE JOKES
Why should we all be encouraged by the story of Jonah and the whale?
AAAAA Because, Jonah was down in the mouth, but came out all right.
Why was everyone in Biblical times so poor?
AAAAA Because there was only one Job!..
How long did Cain dislike his brother?
AAAAA As long as he was Abel.
*********
A Joke about a Pastor
A pastor decided to visit his church members one Saturday. At one particular house it was clear to the pastor that someone was home, but nobody came to the door. The pastor knocked several times and finally took out his card and wrote on the back:
Revelation 3:20 - "Behold, I stand at the door and knock. If anyone hears my voice and opens the door, I will come in and dine with him and he with me."
The next day the same card showed up in the collection plate. Below the pastors message was another scripture passage.
It read Genesis 3:10 - "I heard your voice in the garden, and I was afraid because I was naked and I hid myself."
*********
I have noticed no particular difference in speed with 64-bit vs. 32-bit systems, but 64-bit systems seem to use resources more efficiently. Mind you, that's just an impression.
I have three systems and only one of them is 32-bit at this point.
Generally speaking, for microprocessors these days, "64-bit" is the native mode, and all other modes are "backward compatibility." I suggest that you should, insofar as possible, "keep up with the times." Buy equipment with 64-bit chips and run 64-bit operating systems. Until "128" comes along and the cycle repeats.
I like this answer. "The answer is a SOLID maybe."
When developers and kernel programmers wrote most of the code for 64 bit kernel, programs and drivers, they tended to use newer and faster tools. However many older programs were simply ported or left to 32 bit on older tool chains.
I doubt you'd notice any improvement for desktop use. Using some number crunching tasks would result in maybe at best a small percentage improvement.
The push to 64bit was driven primarily by the need for more directly addressable RAM. PAE works very nicely up to about 16G but after that it 'gets hinky" and many servers and especially supercomputers need hundreds of gigs of RAM. It isn't particularly harder to write code that will run on 64bit hardware but it is substantially more difficult to write 64bit code that actually utilizes 64bit power beyond addressable RAM. This means very few Desktop owners will ever feel a difference beyond the capability for in excess of 16G RAM properly addressed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.