Hi Peter, Peter Tribble wrote: > On Feb 16, 2008 11:14 AM, Jan S Berg <Jan.Berg at sun.com> wrote: > >>>> 2.4 SMF >>>> >>>> We will use the already delivered smf metafile as well as a >>>> smf startup script. We will add a property to the smf service >>>> for choosing between 32 and 64 bit. Default will be the architecture >>>> you are running on. >>>> >>> What's the name of the new property? List it in the exported interface >>> table as well. >>> >> We are proposing to call it "arch", but if there is a standard way of >> naming this >> we would like to use that, although haven't found any. > > The apache is 'httpd/enable_64bit'. While it's some sort of > precedent, and I like it better than 'arch' (which sounds to me > more like sparc vs x86), I'm not entirely convinced.
ok, we will try to go with the same as other components. Unless there are some better alternatives we will use enable_64bit as well. > >>> Is 64bit overwhelmingly always the better choice when running on a >>> 64bit platform? (Enough so that it should be the default?) >>> >> I have not been running that much performance testing with MySQL 32 vs >> 64, but from experience >> with other databases it is not always the best choice. It was pointed >> out by Peter in this thread that >> 64bit version on x86 was mostly the better choice. >> There is no good way of predicting which should be default. > > I would expect that 32-bit is the safe default. On sparc, I wouldn't > expect a benefit in most cases; on x86 then you might have a > system that only runs as 32-bit. > I agree, we also have a softlink from /usr/mysql/bin to /usr/mysql/5.0/bin, and the documentation needs to be consistent how to use 32 vs 64 bit. So after a second thought I think 32bit should always be the default :) Thanks, Jan S
