In today's business, it is increasingly necessary to share workspaces, labs, tools, and any other type of resources. Making the most of the available resources has become a competitive advantage for modern businesses. Booked is open source software written in PHP and MySQL that helps organizations and groups efficiently manage, record and track resources of any kind. It allows you to create schedules so users can find schedules available for resource use.
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 Live 2017 registration bonus!
In this Percona Live featured session, we’ll meet Wei Hu, Staff Engineer at Alibaba. His session (along with co-presenter Dengcheng He, Senior Staff Engineer at Alibaba) is AliSQL: Breakthrough for the Future. AliSQL is a MySQL …[Read more]
In MySQL 8.0 we have been working to improve our support for utf8 as we make the transition to switch it to the default character set. For more details see our earlier posts:
In today’s post I wanted to describe the improvements to support accent and case sensitive collations.…
Query routing is one of the core features of ProxySQL.
Read/write split is perhaps one of the most common query routing use, while the other most commonly used query routing implementation is for sharding.
In this blog post I will show some example on how to implement read/write split.
Read/write split using different ports
If you are using a proxy like HAProxy you can configure it to
listen onto two ports: one as an endpoint for writes, while the
second port as an endpoint for reads.
People has often asked how to configure ProxySQL using the same approach, and routing queries based on incoming port.
Here is an example on how to implement query routing based on incoming port, running the follow on ProxySQL's Admin. I will assume you already have master and slaves configured in the right hostgroups: MySQL writer in hostgroup 10, and MySQL readers in hostgroup 20. A similar approach will apply if you are …[Read more]
You are a DBA, enjoying a good read about the MySQL 8.0.1 development milestone release which contains CTEs. And, window functions are coming in 8.0.2. Perhaps, you think, the analytics team could make good use of window functions to perform rankings on the sales of products compared to the average sales for all the products.
Dreaming about the possibility of trying CTEs in 8.0.1, you get a phone from a user complaining that her ‘SELECT’ statement has been running for a long time.
Fortunately, you have the MySQL Enterprise Monitor (MEM) which is part of the MySQL Cloud Service (MySQLCS). You have recently set up your MySQL database in MySQLCS where you have installed MEM.
You login to your identity domain in MySQLCS and select you service and click the pull-down menu choice ‘Enterprise Monitor URL’:
After logging in, you notice on the MEM dashboard that there is a spike in database activity …[Read more]
In this post, I am going to show you how you can minimize the performance impact of ProxySQL rules by using some finesse.
In my previous post, we could see the effect of the rules on ProxySQL performance. As we could also see, the “apply” option does not help with 1000 tables. Are we sure about this? Let’s consider: if we know 90% of our traffic won’t match any rules, it doesn’t matter if we have 10 or 500 rules – it has to check all of them. And this is going to have a serious effect on performance. How can we avoid that?
Let’s insert rule number ONE, which matches all queries, like this:
insert into mysql_query_rules (username,destination_hostgroup,active,retries,match_digest,apply) values('testuser_rw',600,1,3,'(from|into|update|into table) …[Read more]
The MySQL Development Team is happy to announce the first GA release of InnoDB Cluster–our integrated, native, full stack HA solution for MySQL. You can see highlights of the changes and improvements made since the RC release here, and you can download the GA packages from our MySQL APT (Ubuntu, Debian) and YUM (Redhat, OEL, Fedora) repositories or from dev.mysql.com.…
We carefully listened to the feedback we got from the last release candidate and incorporated some of the suggested changes. On top of that, we have fixed several bugs to reach the desired maturity state.
Here are the highlights of this release!…
MySQL 8.0.1 introduces two new features which allow you to better manage situations where you have tables with hot row contention. This issue frequently presents itself in scenarios such as worker threads all accessing the same tables trying to find new work, and ecommerce websites trying to keep accurate inventory counts.…
[…] Replication filters per channel is now implemented in MySQL starting from version 8.0.1. Check this post for more […]