Not sure about x86, but with opensolaris 2009.06 on sparc, it would probably make more sense to enable 64-bit version by default
- sriram Martin MC Brown wrote: > Hi, > > Yes, the original decision was that we should enable 64-bit on 64-bit > platforms if only for the performance benefits (ignoring the potential > memory access improvements). > > That was made after I did some tests (documented here: > http://coalface.mcslp.com/2008/02/25/comparing-32-bit64-bit-mysql-on-opensolaris/) > > . > > The reason for the 32/64 bit switch *was* the lack of 64-bit support > for some of the more common extensions. This is, AFAIK, still a > problem today with some of the packages shipped with OpenSolaris which > are 32-bit only and expect to use the 32-bit libs. > > In theory, though, you shouldn't have any problems accessing MySQL in > 64-bit using 32-bit libs, but possibly the current organization > doesn't allow for it, because switching to 64-bit enables the 64-bit > libs as the default. > > For us to enable 64-bit MySQL on 64-bit platforms by default, we're > going to need to be sure that all the associated components are 64-bit > too. > > MC > > On 13 Jan 2009, at 20:36, Sriram Natarajan wrote: > > >> Matt / Nico >> If I am not mistaken, there was some discussion during the initial >> design stages as to whether should we enable MySQL as 64-bit in a 64- >> bit >> platform. I guess, the outcome is what we have today :-) I will let >> MySQL folks chime in for more appropriate insight. >> >> - Sriram >> >> Matt Ingenthron wrote: >> >>> Hi Nico, >>> >>> I've cc'd webstack-discuss, as that's the project which does the >>> integration of components like MySQL into OpenSolaris. It's probably >>> best to discuss this there. >>> >>> More below... >>> >>> Nico Sabbi wrote: >>> >>> >>>> On Tuesday 13 January 2009 11:28:54 Nico Sabbi wrote: >>>> >>>> >>>> >>>>> As for $subject: I can't imagine an application that requires 64 >>>>> bit more than a db, but unfortunately the version pkg installs is >>>>> 32-bits only. >>>>> >>>>> >>>>> >>>>> >>>> uhm, sorry I have to backtrack. I've read just now that it's >>>> possible >>>> to configure the 64bit mode with >>>> >>>> $ svccfg -s svc:/application/database/mysql:version_50 setprop >>>> enable_64bit = boolean: true >>>> >>>> $ svcadm refresh mysql >>>> >>>> $ svcadm restart mysql >>>> >>>> but it would have been nice enabling it by default on a 64bit >>>> installation :) >>>> >>>> >>> Correct. With other components, notably Apache/PHP, we'd decided to >>> keep 64-bit an SMF configurable option since it's possible/likely >>> that >>> 3rd party extensions people may add through pecl/apxs could not be >>> 64-bit clean. >>> >>> You have a good argument for MySQL *if* using the InnoDB query cache. >>> It's still pretty common though for people to rely on the >>> filesystem for >>> caching (and ZFS should do well for this type of configuration) for a >>> variety of reasons. >>> >>> I'm not sure what the right approach is, but maybe one of my >>> colleagues >>> on webstack-discuss has thought about this already. I'd imagine we >>> can >>> do this from the service... perhaps pre-deliver it with an >>> enable_64bit >>> set to "auto" (which would mean it can't be a boolean any longer) and >>> use /usr/lib/isaexec within the service? >>> >>> - Matt >>> _______________________________________________ >>> >>> >>> webstack-discuss mailing list >>> webstack-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >>> >>> >> _______________________________________________ >> >> >> webstack-discuss mailing list >> webstack-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >> >> > > -- > Martin 'MC' Brown, mc at mcslp.com and mc.brown at sun.com > Technical Writer, Database Group, Sun Microsystems > Everything MCslp: http://planet.mcslp.com > > _______________________________________________ > > > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
