Indeed, MySQL 5.7 rocks ;-)
This is the part1 of the following blog posts about various
benchmark results on MySQL 5.7 - and this particular one is
dedicated to the Sysbench OLTP_RO Point-Select 8-tables
workload.
We've already published the over 500K QPS on SQL Point-Selects
before @32cores-HT server, so may reconfirm it again with MySQL
5.7 DMR5 -vs- other engines :
and now on a similar server, but with 40cores-HT we're able to
confirm 645 QPS on the same workload!
If you missed the long story about how we arrived on such a
performance level and how to reproduce the test - you may find
all here. This workload is the most killing from
all Read-Only Sysbench OLTP tests.. And it's really for the first
time we started to scale here with MySQL! …
In this third installment in this series, I'll explain why the
smart solution I described in the previous post actually wasn't that good, and
then I go on to explain how to fix it, and why that fix wasn't
such a smart thing after all. So, this was the design we ended
with last time:
We have Oracle replicating to a Materialized
View, this to ensure that we can run triggers when the is a
commit, and then triggers on this Materialized View updates
MariaDB by sending a UDP message to a server that in turn is
connected to MariaDB.
The issue with the above thingy was that a Materialized View by
default is refreshed in it's entirety when there is a refresh, so
if the table has 10.000 rows and 1 …
Business Wire Oracle Open World 2014, Booth # 430- Continuent, Inc., a leading provider of open source database clustering and replication solutions, today announced Continuent Tungsten 3.0, a powerful solution that combines advanced clustering and replication technologies to meet the transaction processing and analytic needs of the entire business. Continuent Tungsten 3.0 enables constant,
We have relocated the MySQL Connector/Python repository on GitHub to the following location:
https://github.com/mysql/mysql-connector-python
The old location will redirect to the above URL.
No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.
We have relocated the MySQL Connector/Python repository on GitHub to the following location:
https://github.com/mysql/mysql-connector-python
The old location will redirect to the above URL.
No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.
The theme for this series of posts is, and indicated in the
previous post, "Try and try, again", and there
will be more of this now when I start to make this work by
playing with Oracle, with PL/SQL and with the restrictions of
Oracle Express (which is the version I have available).
So, what we have right now is a way of "sending" SQL statements
from Oracle to MariaDB, the question is when and how to send them
from Oracle. The idea for this was then to use triggers on the
Oracle tables to send the data to MariaDB, like this, assuming we
are trying to replicate the orders table from Oracle to
MariaDB:
In Oracle, and assuming that the
extproc I have that created to send UDP …
MySQL is the database of choice for most OpenStack components (Ceilometer is a notable exception). If you start with a small deployment, it will probably run like a charm. But as soon as the dataset grows, you will suddenly face several challenges. We will write a series of blog posts explaining the issues you may hit and how to overcome them.
Where is MySQL used in OpenStack?
Have a look at the logical diagram of OpenStack below (click the image for a larger view).
The diagram is a bit outdated: Neutron appears as Quantum and newer components like Heat are not pictured. But it shows that a database has to be used to store metadata or runtime information. And although …
[Read more]MySQL Connector/Python v2.0 goes GA with version 2.0.1 GA. It is available for download from the MySQL Developer Zone! The previous post about 2.0 described what changed and what was added, here’s an overview:
- Incompatibilities
- Supported Python: 2.6 and 2.7 and 3.3 and 3.4
- Raw Cursors Return bytearray Objects
- LOAD LOCAL DATA INFILE On by Default
- New features
- New Cursors return dictionaries and named tuples
- Options Files Support Added
- Packaging and support files removed …
We are very happy to introduce a new MySQL utility named
'mysqlbinlogmove', which is used to relocate binary log files.
This utility is one of two new utilities included in MySQL
Utilities release-1.6.0 Alpha. The other utility is
'mysqlgrants', which is used to display the privileges (grants)
of database objects.
Note: I use "binary log" to refer to both "kinds" of binary log
files (binlog and relay log files) in general, and use "binlog"
to refer specifically to those that are not "relay log"
files.
The mysqlbinlogmove utility allows you to move binary log files
to a new location taking care of correctly updating the
respective index file for you. This utility can be very useful if
you want to change the location to store the binlog file and you
want to move all of the binary log files. It is also handy to
archive older binary log files to a new location thereby saving
disk space in the server's partition.
…
We are very happy to introduce a new MySQL utility named “mysqlbinlogmove“, which is used to relocate binary log files. This utility is one of two new utilities included in MySQL Utilities release-1.6.0 Alpha. The other utility is “mysqlgrants“, which is used to display the privileges (grants) of database objects.
Note: I use “binary log” to refer to both “kinds” of binary log files (binlog and relay log files) in general, and use “binlog” to refer specifically to those that are not “relay log” files.
The mysqlbinlogmove utility allows you to move binary log files to a new location taking care of correctly updating the respective index file for you. This utility can be very useful if you want to change the location to store the binlog file and you want to move all of the binary log files. It is also handy to archive older binary log files to a new location thereby saving disk …
[Read more]