> What would concern me is the guy evaluating OpenSolaris, grabbing an > extension that's needed for his application, running > gem/apxs/phpize/pecl and then seeing it blow up. The install readme > won't likely have an "if you're on OpenSolaris" branch, and it may not > even be clear where the problem is. The quick conclusion someone > could > come to in that case is that Web Stack is broken... not what we want.
That would be one of my concerns as well, but I don't know where the 64 vs 32 bit MySQL implementation would be a problem point here. Let me start out by saying that the different in performance for MySQL in 32 and 64 bit is pretty much identical. The benefits come from being able to use vast quantities of memory for caches (MySQL, afterall, likes to make the assumption that it's the only process on the machine and therefore has a bad habit of wanting lots of memory if that's the type of application you are using). The only issues in terms of third party apps and extensions will be that final interface to MySQL - everything else will talk through the native environment to whatever the interface is. For example, if you are using Perl and DBI, DBD::mysql needs to know how to talk to MySQL natively, but mod_perl doesn't need to know how to do this. I'm not arguing for 64-bit by default on 64-bit capable hardware, but I don't see a technical reason why it should cause a problem in the example you give. I would certainly be more concerned about other extensions to other environments/languages/frameworks for this reason though. MC (also mc at mysql.com) -- Martin 'MC' Brown, mc at mcslp.com Everything MCslp: http://planet.mcslp.com
