Percona is glad to announce the new release of Percona XtraDB Cluster 5.6 on June 3rd 2015. Binaries are available from downloads area or from our software repositories.
Based on Percona Server 5.6.24-72.2 including all the bug fixes in it, Galera Replicator 3.11, and on …
[Read more]A quick question, which I’ve asked once before –
if you were an Oracle DBA, then learned MySQL, what do you wish you knew before you got started?
Also, what was helpful to you as you learned? (Websites, #mysql on irc, documents, etc.) What do you wish you had (or want to have now) if you are a DBA for both Oracle databases and MySQL databases?
Ie, what would be good to give an Oracle DBA who wants to start learning or supporting MySQL as well? Please respond with comments here, or directly email me at ben-dot-krug-at-oracle-dot-com.
Thanks!
English: Madrid MySQL Users Group will be holding their next meeting on 17th June at 18:00h at EIE Spain in Madrid. Dimitri Vanoverbeke and Stéphane Combaudon from Percona will be offering two presentations for us: Practical MySQL optimisations Galera Cluster – introduction and where it fits in the MySQL eco-system I think this is an excellent moment … Continue reading MMUG13: Practical MySQL Optimisation y Galera Cluster presentations
The post MMUG13: Practical MySQL Optimisation y Galera Cluster presentations first appeared on Simon J Mudd's Blog.
In the MySQL ecosystem there are few load balancers there are
also open-source, and ProxySQL is one of the few proxies that
works at the application layer and therefore is SQL aware.
In this blog post we will benchmark ProxySQL against MaxScale,
another popular proxy for MySQL.
The idea to compare ProxySQL vs MaxScale came after reading an
interesting blog post of Krzysztof Książek on SQL Load
Balancing Benchmark, comparing performance of MaxScale vs
HAProxy.
Disclaimer: ProxySQL is not GA yet, therefore please do not
use it in production.
Sysbench setupI wanted to setup a similar sysbench setup to what
Krzysztof used in his benchmark, but it is slightly
different:
a) instead of using a MySQL cluster with Galera, I setup a
cluster with 1 master …
Following the release of ClusterControl 1.2.10 a week ago, we are excited to demonstrate this latest version of the product on Tuesday next week, June 9th.
Join our CTO, Johan Andersson, who will be discussing and demonstrating the new ClusterControl DSL, Integrated Developer Studio and Database Advisors, which are some of the cool new features we’ve introduced with ClusterControl 1.2.10.
New Features Webinar: ClusterControl 1.2.10
DATE & TIME
Europe/MEA/APAC
Tuesday, June 9th at 09:00 (UK) / 10:00 CEST (Germany, France,
Sweden)
…
Some applications have a heavy write workload on a few records – for instance when incrementing a global counter: this is called a write hotspot. Because you cannot update the same row simultaneously from multiple threads, this can lead to performance degradation. When using Percona XtraDB Cluster (PXC), some users try to solve this specific issue by writing on multiple nodes at the same time. Good idea or bad idea? Read on!
Simultaneous writes on a standalone InnoDB server
Say you have these 3 transactions being run simultaneously (id is the primary key of the table):
# T1 UPDATE t SET ... WHERE id = 100 # T2 UPDATE t SET ... WHERE id = 100 # T3 UPDATE t SET ... WHERE id = 101
All transactions will require a row lock on the record they want to modify. So T3 can commit at the same time than T1 and/or T2, because it will …
[Read more]When I started writing this post I planned to follow up on my series of posts by creating a unique constraint with more than 16 columns using a MariaDB virtual column the same way I used a MySQL generated column in my most recent post. During my testing I abandoned that plan when I discovered two things:
Tue, 2015-06-02 19:07geoff_montee_g
Most MariaDB users are probably aware of the privilege system available in MariaDB and MySQL. Privileges control what databases, tables, columns, procedures, and functions a particular user account can access. For example, if an application stored credit card data in the database, this data should probably be protected from most users. To make that happen, the DBA might disallow access to the table or column storing this sensitive data.
However, sometimes the privilege system isn't sufficient to secure data. Sometimes data needs to be secured beyond tables and columns. In those cases, row-level security (sometimes abbreviated RLS) may be necessary. Possible use cases for row-level security are:
In my previous post, I showed you a way to store tweets in MySQL, and then use Perl to automatically publish them on Twitter.
In this post, we will look at automatically sending a “thank you” to people who retweet your tweets — and we will be using Perl and MySQL again.
Just like in the first post, you will need to register your application with Twitter via apps.twitter.com, and obtain the following:
consumer_key consumer_secret access_token access_token_secret
One caveat: Twitter has a rate limit on how often you may connect with your application — depending upon what you are trying to do. See the Rate Limiting and …
[Read more]It seems these days if anyone knows anything about tuning InnoDB, it’s that you MUST tune your innodb_buffer_pool_size to 80% of your physical memory. This is such prolific tuning advice, it seems engrained in many a DBA’s mind. The MySQL manual to this day refers to this rule, so who can blame the DBA? The question is: does it makes sense?
What uses the memory on your server?
Before we question such advice, let’s consider what can take up RAM in a typical MySQL server in their broad categories. This list isn’t necessarily complete, but I think it outlines the large areas a MySQL server could consume memory.
