On Mon, 2010-08-16 at 14:36 +0000, oxala wrote:
> Hello All,
>
> I am just curious … who uses a 64bit os … and more interesting
> … why?
Well… there’s the common answers like performance and memory.
Certainly one could argue that 32bits is fine if less than 4G (esp less
than 3.5G usable).
But, my own experience NOW is that 64bits is important for future
FEATURES. For example, virtualization options will require CPU features
and we’re seeing a lot of push to 64bit. Granted, running a hypervisor
on top of an OS is passe… and perhaps it will not be a restriction
there but only for bare metal hypervisors in which case the point it
moot.
>
> The question is not intended for the “I run a mega-monster-database”
> crowd. I know why yall like the extra bits … see below … 
>
> I’m interested in the personal workstation.
Actually, you’re interested in a low end personal desktop and NOT a
workstation. The workstation moniker carries a higher end usage with
it. So, we’ll assume large memory there.
There are lots of things that will continue to require more and more
memory and just like 256M was plenty for your “workstation” not too many
years ago, 4G will seem equally as small in the near future.
>
> Background:
>
> Going back to the early 90’s, it is very easy to see the appeal of
> mainstream applications capable of addressing 32bits of memory. It’s
> NOT difficult to hit the 16bit address space limit using something like
> Lotus 1-2-3 or Microsoft’s Excel. I remember this happening to many
> non-geek colleagues.
>
> 32bit addresses 4GB of memory. This trivial piece of information
> almost answers the “why?”. If you run an application that
> requires/likes more than 4GB memory (hello again mega-monster-database
> folk) … bingo! I’d love to know what commonly used applications are
> so greedy, assuming there are such apps.
Lots of things are cached… including the filesystem. Having more
memory can mean a huge performance increase in the areas of shared
filesystems in particular. So… even if you just run a couple of
apps… you might see some real benefit if you happen to run shared
filesystems as well.
>
> For the use case scenario of many apps in a 32bit environment, PAE
> allows the kernel to work with up to 64GB of memory, so that multiple
> memory-hungry 32bit apps can run side by side. Is there a distinct
> advantage of native 64bit for this use case? Is there a common
> perception of a native 64bit advantage here?
PAE does NOT allow you to violate the 2G limit on individual processes
(a limit that is there because of 32bit). So… while it’s nice to say
that PAE saves the day… it’s really only useful if running a lot
processes.
>
> My final question: any folk who can’t like without 64bit emacs?
Excellent point… when editing files, old vi was simply not good enough
because it assumed how big of a file could be handled and it was quickly
surpassed. Moving forward, the idea of bringing up a 2G+ file is
certainly not out of the question… so 64bits could be useful there as
well.