I plan to install PHP on a system running on AMD Opteron/Windows Server 2008/IIS7. According to the device manager the OS is a 64-bit Operating System. So which flavor of PHP should I install on it. If 64-bit PHP 5.3.x then will there be any gotchas? Or should I expect 32-bit PHP to run smoothly without any (performance) problems?
PS: in case you're wondering -- WPI sucked and did not work at all. It tried to download 32-bit/NTS version of PHP for Windows and failed repeatedly.
I'm going to install Ubuntu 10.04 Server in a virtual machine and want run MySQL and Lighttpd on it.
Are there any benefits or disadvantages between 64-bit and 32-bit virtualization, except the 4 gigabyte memory limit on 32-bit machines.
I use Virtualbox.
I've got a server with 64GB RAM installed (reported in both the bios and in Windows), but the system information from control panel displays the fact that only 32GB of this is usable.
I've only ever seen this with 32bit windows when there's too much RAM installed before.
It also seems unlikely that precisely half of the RAM is dodgy? Any ideas?
Many thanks
James (warning: dev playing at server admin)
(I've read a lot about 64-bit versus 32-bit OS/Apps, but this question is specifically in regards to databases.)
I'm trying to understand the pros and cons of 32-bit versus 64-bit databases, and namely, under what conditions that it starts to make sense to use 64-bit installations.
The database systems that I am interested in are: SQL Server 2008, MySQL, and PostgreSQL 9.0.
I have read that pre-9.0 versions of PostgreSQL only comes in 32-bit for Windows, and this article about running 32-bit PostgreSQL on 64-bit Windows clears up some of my confusion, but I'm looking for more info.
When would I benefit from using 64-bit databases (i.e. database size/disk space, available system memory, types of data sernarios that are known to benefit from it, which database engine being used, etc.)?
Besides the advantages of 64-bit memory allocation (> 4 GB - see this question on StackOverflow for why 32-bit +4 GB solutions won't work for me), what other reasons do I have for recommending that we should host an ASP.NET website on 64-bit Windows Server 2008, as opposed to the 32-bit version?
If it's only the larger addressable memory (>4 GB) issue, we have a load-balanced solution anyway so we could scale by adding a new (virtual) box.
The CPUs won't be running hot either, so any marginal speed gains couldn't be justified.
My own gut feeling is that we should host on 64-bit if we can, purely because it's easier to scale (by plugging in more RAM when we need to). But is that it?!
All comments and ideas are welcome!