On 07.08.2012, at 13:47, Daniel Danger <[email protected]> wrote:
> On 08/06/2012 08:26 PM, Frank Karlitschek wrote: >> Also MyISAM is faster and is using less resources in situation where you >> have significantly more read than write operations. > > Do you have a source for that? I just stumbled over [1], suggesting > otherwise. > > Cheers > Daniel This depends heavily on the usecase of course so my statement was perhaps a bit too broad. I collected a lot of experience in this area as part of my old job and my old startup. In both cases we handled significant traffic with mysql (over 10 million page impressions per day) MySQL suggests to use myisam in this usecases too. That´s one of the cool things about mysql in my experience that they have different storage engines that are ideal in different usecases. So we should analyze our tables how the access pattern looks like and pick the optimal storage engine for it. Frank _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
