Tag - open source databases

Percona’s Open Source Data Management Software Survey


Click Here to Complete our New Survey!
Last year we informally surveyed the open source community and our conference attendees.
The results revealed that:

48% of those in the cloud choose to self-manage their databases, but 52% were comfortable relying on the DBaaS offering of their cloud vendor.
49% of people said “performance issues” when asked, “what keeps […]

Read more

Percona Live Open Source Database Conference Europe 2017 in Dublin, Ireland Call for Papers is Open!

Colin Charles

Announcing the opening of the Percona Live Open Source Database Conference Europe 2017 in Dublin, Ireland call for papers. It will be open from now until July 17, 2017.*
Do you have a big idea to explain, use case to share or skill to teach? Submit your speaking proposal for either breakout or tutorial sessions. […]

Read more

Percona Live Webinar Thursday, April 6, 2017: Best Practices Migrating to Open Source Databases

Please join Percona’s CEO and Founder, Peter Zaitsev on April 6th, 2017 at 8:00 am PDT / 11:00 am EDT (UTC-7) as he presents Best Practices Migrating to Open Source Databases.
Register Now

This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in […]

Read more

Percona Live Featured Session: Using SelectStar to Monitor and Tune Your Databases

Welcome to another post in the series of Percona Live featured session blogs! In these blogs, we’ll highlight some of the session speakers that will be at this year’s Percona Live conference. We’ll also discuss how these sessions can help you improve your database environment. Make sure to read to the end to get a special Percona […]

Read more

Open Source Databases on Big Machines: Does READ COMMITTED Scale on 144 Cores?


In the second post in my series on open source databases on big machines, we’ll look at whether READ COMMITTED scales with multiple cores.
The default transaction level for InnoDB is
REPEATABLE READ. A more permissive level is 
READ COMMITTED, and is known to work well. While the 
REPEATABLE READ level maintains the transaction history up to the start […]

Read more