From: Reindl Harald
Date: April 28 2012 8:01am
Subject: Re: engine is now innoDB instead of MyISAM.
List-Archive: http://lists.mysql.com/mysql/227260
Message-Id: <4F9BA3CB.2090603@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig9BF5E86E31DAE43D2DC14094"

--------------enig9BF5E86E31DAE43D2DC14094
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 28.04.2012 09:00, schrieb Brown:
> We recently switched from MySQL community to Mysql clustered using Orac=
le supported MySQl. The problem is, during our testing phase, we observed=
 the default engine is now innoDB instead of MyISAM. Any thoughts on that=
? We're not getting the performance that we expected - any thoughts or ad=
vices out there will be greatly appreciated.

my.cnf: default-storage-engine =3D myisam

you cann not compare MyISAm and InnoDB for the same workloads
that's why my.cnf exists and we usually define each known setting
to prevent chnages in the behavior of applications by software-updates

the same for "php.ini"


--------------enig9BF5E86E31DAE43D2DC14094
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+bo8sACgkQhmBjz394AnmmGACcDun5eiIiEy3alcQhGk2mC+l7
eCcAn3CixHMohFTZJSCf2j9IqxdFzVKO
=hzQ/
-----END PGP SIGNATURE-----

--------------enig9BF5E86E31DAE43D2DC14094--