[Building Sakai] Rutgers is now using innodb-plugin in production

[Jennings, Michael]

At UNC we are using MySql 5.5 Enterprises edition with Sakai 2.7.0 without any issues so far.

We are also in the process of upgrading to 2.8.1 and  things look good so far

Mike

Mike



-------- Original message --------
Subject: Re: [Building Sakai] Rutgers is now using innodb-plugin in production
From: Steve Swinsburg <steve.swinsburg at gmail.com>
To: Hedrick Charles <hedrick at rutgers.edu>
CC: "sakai-dev at collab.sakaiproject.org Developers" <sakai-dev at collab.sakaiproject.org>


Any version pre 2.9 doesn't work too well but post 2.9 may be ok. YMMV though and it hasn't been QA'd or endorsed, only 5.1.

cheers,
Steve



On 20/12/2011, at 11:14 AM, Hedrick Charles wrote:

> No. My understanding was that Sakai wasn't supported for 5.5.
>
> On Dec 19, 2011, at 6:46:05 PM, Robert Cohen wrote:
>
>>
>> Did you evaluate mysql 5.5?
>> From what I've read its supposed to have performance improvements over 5.1
>> even with the innodb plugin.
>>
>>
>>
>> On 20/12/11 5:54 AM, "Charles Hedrick" <hedrick at rutgers.edu> wrote:
>>
>>> We've had two episodes of the database server going to 100%. Because some
>>> of my tests have shown that innodb-plugin works better under some kinds
>>> of load, we're moving to it. We also had a DNS problem that might have
>>> contributed to this. It's been fixed, so if our problems don't come back
>>> we may not be sure what caused it.
>>>
>>> We're using old versions of mysql 5.1, simply because we haven't wanted
>>> to upgrade in the middle of the year, 5.1.44 with innodb plugin 1.0.6.
>>> We'll probably be moving from our Solaris-based server to a server on
>>> Linux running the newest 5.1, in late January. It's the final part of our
>>> new Xenserver / iSCSI virtual architecture. After looking at various test
>>> results I've decided to run the new system with hypertheading on. Innodb
>>> plugin should deal with the multicore scaling problems sufficiently for
>>> that to make sense.
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>
>>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20111220/c0334925/attachment.html