From: Leonid Eremin <leon.programmer@gmail.com>
To: "Dustin J. Mitchell" <gentoo-amd64@lists.gentoo.org>
Subject: Re[2]: [gentoo-amd64] 32 or 64 for web server and mysql
Date: Fri, 20 Jul 2007 19:09:29 +0400 [thread overview]
Message-ID: <1277511570.20070720190929@gmail.com> (raw)
In-Reply-To: <20070720144310.GJ3830@v.igoro.us>
On AMD64 there's also number of named general-purpose registers is
increased from 8 to 16 - new capabilities for optimization :)
> On Fri, Jul 20, 2007 at 09:21:10PM +0800, P.V.Anthony wrote:
>> The reason for this questions is that there are some information on the
>> net that says that there is no much difference between them.
>> Is that true? Thought that 64bit is always better.
> Building a system 64-bit buys you:
> - wider integers (so math with 64-bit integers is faster)
> - wider pointers (so an application can have a *lot* more address space
> allocated to it)
> - bigger binaries and data structures (so more RAM consumed)
> - future-proofing (in a few years, 32-bit hardware will not be
> available new)
> There's no "better" and it's not inherently faster in any way. As
> another poster said, most UNIX apps have been running 64-bit on other
> architectures (SPARC being the most common) for years, so compatibility
> isn't a big deal.
> Those are the points on which I base my 32/64 decisions.
> Dustin
--
С уважением,
Leonid mailto:Leon.Programmer@gmail.com
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-20 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 13:21 [gentoo-amd64] 32 or 64 for web server and mysql P.V.Anthony
2007-07-20 13:39 ` Mark Haney
2007-07-20 14:23 ` Bob Sanders
2007-07-20 14:43 ` Dustin J. Mitchell
2007-07-20 15:09 ` Leonid Eremin [this message]
2007-07-20 15:20 ` Daniel Gryniewicz
2007-07-20 15:36 ` Antoine Martin
2007-07-20 18:08 ` [gentoo-amd64] " Duncan
2007-07-23 2:33 ` P.V.Anthony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1277511570.20070720190929@gmail.com \
--to=leon.programmer@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox