Some time ago, feedback was requested on new replication default after MySQL 5.7. Some of the suggested default are:
relay-log-info-repository = TABLE (previous default FILE) relay-log-recovery = ON (previous default OFF) master-info-repository = TABLE (previous default FILE) sync-master-info = 1,000 (previous default 10,000) sync-relay-log = 1,000 (previous default 10,000)
I agree on the
Recently a colleague of mine ask me to provide a simple example
on how ProxySQL can perform sharding.
ProxySQL is a very powerful platform that allow us to manipulate
and manage our connections and query in a simple but effective
way.
In this article I will show you how.
{autotoc enabled=yes}
Before starting is better to clarify some basic concepts.
ProxySQL organize its internal set of servers in Host Groups (HG), each HG can be associate to users and to Query Rules (QR).
Each QR can be final (apply = 1) or can let ProxySQL continue to parse other QR.
A QR can be a rewrite action, or can be a simple match, it can have a specific target HG, or be generic, finally QR are defined using regex.
You can see QR as a sequence of filters and transformation that you can arrange as you like.
These simple basic rules give us enormous flexibility, …
[Read more]
Recently a colleague of mine ask me to provide a simple example
on how ProxySQL can perform sharding.
ProxySQL is a very powerful platform that allow us to manipulate
and manage our connections and query in a simple but effective
way.
In this article I will show you how.
{autotoc enabled=yes}
Before starting is better to clarify some basic concepts.
ProxySQL organize its internal set of servers in Host Groups (HG), each HG can be associate to users and to Query Rules (QR).
Each QR can be final (apply = 1) or can let ProxySQL continue to parse other QR.
A QR can be a rewrite action, or can be a simple match, it can have a specific target HG, or be generic, finally QR are defined using regex.
You can see QR as a sequence of filters and transformation that you can arrange as you like.
These simple basic rules give us enormous flexibility, …
[Read more]Motivation Melbourne just won the “most liveable city 2016”, the 5th time in a row. That’s awesome, but it comes with a price, and the one you’d think of: internet here sucks! Sounds weird, isn’t it? Well, one of the reasons Melbourne is such a great city, is it’s size, the amount of people in [...]
Thank you for attending my 22nd July 2016 webinar titled “Top Most Overlooked MySQL Performance Optimizations“. In this blog, I will provide answers to the Q & A for that webinar.
For hardware, which disk raid level do you suggest? Is
raid5 suggested performance-wise and
data-integrity-wise?
RAID 5 comes with high
overhead, as each write turns into a sequence of four physical
I/O operations, two reads and two writes. We know that RAID 5s
have some write penalty, and it could affect the performance on
spindle disks. In most cases, we advise using alternative
RAID levels. Use RAID 5 when disk capacity is more important than
performance (e.g., archive databases that …
I know this is a tad late, but there have been some changes, etc. recently, so apologies for the delay of this post. I still hope to meet many of you to chat about MySQL/Percona Server/MariaDB Server, MongoDB, open source databases, and open source in general in the remainder of August 2016.
Percona announces the release of Percona Server 5.5.51-38.1 on August 19, 2016. Based on MySQL 5.5.51, including all the bug fixes in it, Percona Server 5.5.51-38.1 is now the current stable release in the 5.5 series.
Percona Server is open-source and free. You can find release details of the release in the 5.5.51-38.1 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.
Bugs Fixed: …
[Read more]With MySQL version 5.7.12 and up, Oracle continues to improve MySQL’s security features by adding MySQL Enterprise Transparent Data Encryption (TDE) for InnoDB tables stored in innodb_file_per_table tablespaces. This feature provides at-rest encryption for physical tablespace data files.
MySQL Enterprise TDE uses a two-tier encryption key architecture, consisting of a master encryption key and tablespace keys.…
MySQL 5.7/8.0 does not allow creating a full-text index on a JSON column. Although a full-text index would be useful – unstructured data deserves unstructured search. I am unaware o any workaround of this limitation that does not require storing the JSON data twice. Then I started messing around, allowed indexing of JSON columns, saw great execution times but eventually followed MySQLs’ decision to call it a day. Friday afternoon rambling on indexing and easy hacking…
Why full-text: JSON indexing limitations and pitfalls
The current version of the MySQL Document Store is not yet optimized for performance. When we started this effort, we quickly gathered a long list of features that we considered a must have prior to any serious performance tuning. The teams focussed building infrastructure and delivered many …
[Read more]It is soon time for the annual Oracle OpenWorld conference in San Francisco. This year it takes place from 18 to 22 September. There will be a wide range of talks about MySQL and other Oracle products with speakers including Oracle developers, product management, Support, customers, and community members. So there should be something for everyone.
MySQL Support will have two talks this year:
| Time |
Session |
Title |
Room |
Presenter |
|
Monday 11:00am - 01:00pm |
TUT1718 |
MySQL DBA Primer |
Park Central—Stanford | Lig Isler-turmelle |
