Re: i386 with PAE or AMD64 on PowerEdge with 4G RAM

On 6/19/07, Martin Turgeon <turgeon.martin@xxxxxxxxx> wrote:
2007/6/18, Jeremy Chadwick <koitsu@xxxxxxxxxxx>:
>
> On Mon, Jun 18, 2007 at 01:03:44PM -0400, Martin Turgeon wrote:
> > I just receive 2 PowerEdge servers (a 1950 and a 860) both with 4G of
> RAM. I
> > installed FreeBSD 6.2 Release i386 on both of them. Unfortunately, only
> 3,5G
> > is recognized on the 860 and 3,3G on the 1950.
> > dmesg on 860:
> > real memory = 3757834240 (3583 MB)
> > avail memory = 3678318592 (3507 MB)
> >
> > I am facing a difficult decision. Should I use i386 with PAE enabled in
> the
> > kernel (I read a lot of warnings using it) or should I go with AMD64?
> Which
> > branch should I follow?
>
> Based on what I've read from some of the porters and miscellaneous
> others, generally-speaking there's too many issues with amd64 (in the
> sense of 32-bit vs. 64-bit compatibility -- not the fault of the kernel
> or otherwise) to consider it worth switching to.
>
> I personally don't run 64-bit OSes because most developers still use
> 32-bit machines and don't have a way to develop/test in 64-bit
> environments.
>
> That said, I'd recommend you stick with i386 + PAE, simply for
> guaranteed application compatibility.


My setup is fairly standard (as I described), should I expect problem with
64 bit version of these programs?


You'll lose the amount of RAM you're seeing due to PAE addressing for
> PCI address space. I can dig you up a usage map (broken down by how
> much is taken up by each portion; PCI, ACPI, etc.) if you want one.
> It's for SuperMicro systems, but the general idea applies to most
> everything.


I'm not sure to understand what you mean by that. Are you saying that PAE
will eat the 500M that should be available?

--
> | Jeremy Chadwick jdc at parodius.com |
> | Parodius Networking http://www.parodius.com/ |
> | UNIX Systems Administrator Mountain View, CA, USA |
> | Making life hard for others since 1977. PGP: 4BD6C0CB |

If I were you, I would go for AMD64.


--
Regards,

-Abdullah Ibn Hamad Al-Marri
Arab Portal
http://www.WeArab.Net/
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: performance: store.exe uses 579Mb only out of 4Gb
    ... RAM is mainly used by store.exe in the form of database page buffers. ... You'll find more information on optimizing memory for Exchange in: ... The fact that you're using optin implies that you have a server based on ... response from the vendor is to do something to enable PAE, ...
    (microsoft.public.exchange.admin)
  • RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB without PAE (long)
    ... > work fine with!PAE. ... vmstat -m is useful to keep track of kernel memory use. ... When we have removed some RAM, in other words, install 2GB memory on the ... I think this is important, however, I got no reason why a server ...
    (freebsd-current)
  • RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB without PAE (long)
    ... > work fine with!PAE. ... vmstat -m is useful to keep track of kernel memory use. ... When we have removed some RAM, in other words, install 2GB memory on the ... I think this is important, however, I got no reason why a server ...
    (freebsd-stable)
  • Re: 4GB RAM with an intel core 2 processor
    ... When I install the 2 extra memory modules, the kernel tells me on startup ... I took a quick look at PAE and discovered that the PAE kernel is ... Do I have any options for using my 4GB of RAM and still retain USB and the nvidia driver? ...
    (freebsd-current)
  • Re: i386 with PAE or AMD64 on PowerEdge with 4G RAM
    ... generally-speaking there's too many issues with amd64 (in the ... I personally don't run 64-bit OSes because most developers still use ... That said, I'd recommend you stick with i386 + PAE, simply for ... You'll lose the amount of RAM you're seeing due to PAE addressing for ...
    (freebsd-hackers)