This Log Buffer Edition covers various blog posts from the last week regarding Oracle, SQL Server and MySQL.
Oracle:
Percona Live is moving from London to Amsterdam this year and the event is also expanding to three full days. Percona Live Europe 2015, September 21-23, will be at the Mövenpick Hotel Amsterdam City Centre. The call for speakers and Super Saver registration are now open. Hurry though because the deadline for submitting a speaking proposal is June 21st and Super Saver registration ends July 5th!
This year’s conference will feature one day of tutorials and two days of keynote talks and breakout …
[Read more]Greetings everyone! Let’s discuss a 3rd Party auditing solution to MySQL and how we can leverage MongoDB® to make sense out of all of that data.
The McAfee MySQL Audit plugin does a great job of capturing, at low level, activities within a MySQL server. It does this through some non-standard APIs which is why installing and configuring the plugin can be a bit difficult. The audit information is stored in JSON format, in a text file, by default.
There is 1 JSON object for each action that takes place within MySQL. If a user logs in, there’s an object. If that user queries a table, there’s an object. Imagine 1000 active connections from an application, each doing 2 queries per second. That’s 2000 JSON objects per second being written to the audit log. After 24 hours, that would be almost 173,000,000 audit entries!
How does one make sense of that many JSON objects? One option would be to write your own parser in …
[Read more]While our engineering team is working on finalizing the TokuMXse storage engine, I want to provide an experimental build that you can try and test MongoDB 3.0 with our storage engine.
It is available here
percona.com/downloads/TESTING/Percona-TokuMXse-rc5/percona-tokumxse-3.0.3pre-rc5.tar.gz
To start MongoDB with TokuMXse storage engine use:
mongod --storageEngine=tokuft
I am looking for your feedback!
The post MongoDB with Percona TokuMXse – experimental build RC5 is available! appeared first on MySQL Performance Blog.
Being schemaless is one of the key features of MongoDB. On the bright side this allows developers to easily modify the schema of their collections without waiting for the database to be ready to accept a new schema. However schemaless is not free and one of the drawbacks is write amplification. Let’s focus on that topic.
Write amplification?
The link between schema and write amplification is not obvious at first sight. So let’s first look at a table in the relational world:
mysql> SELECT * FROM user LIMIT 2; +----+-------+------------+-----------+-----------+----------------------------------+---------+-----------------------------------+------------+------------+ | id | login | first_name | last_name | city | country | zipcode | address | password | birth_year | …[Read more]
Last week I wrote up my thoughts about the Percona acquisition of
Tokutek from the perspective of TokuDB and TokuMX[se]. In this third blog of the trilogy
I'll cover the acquisition and the future of the Fractal Tree
Index. The Fractal Tree Index is the foundational technology upon
which all Tokutek products are built.
So what is a Fractal Tree Index? To quote the Wikipedia page:
"a Fractal Tree index is a tree data structure that keeps data
sorted and allows searches and …
An idea for a benchmark based on the “arrival request” rate that I wrote about in a post headlined “Introducing new type of benchmark” back in 2012 was implemented in Sysbench. However, Sysbench provides only a simple workload, so to be able to compare InnoDB with TokuDB, and later MongoDB with Percona TokuMX, I wanted to use more complicated scenarios. (Both TokuDB and TokuMX are part of Percona’s product line, in the case you missed Tokutek now part of the Percona family.)
Thanks to Facebook – they provide LinkBench, a benchmark that emulates the social graph …
[Read more]
A few days ago I wrote up my thoughts about the Percona acquisition of
Tokutek with respect to TokuDB. In this blog I'm going to do
the same for TokuMX and TokuMXse. And in a few days I'll wrap up
this trilogy by sharing my thoughts about Fractal Tree
Indexes.
Again, when I'm writing up something that I was very involved
with in the past I think it's important to disclose that I worked
at Tokutek for 3.5 years (08/2011 - 01/2015) as VP/Engineering
and I do not have any equity in Tokutek or Percona.
Since much of the MySQL crowd might be hearing about Tokutek's
"other products" for the first time I'll provide a little history
of both of the products before I dive in deeper.
TokuMX is a fork of MongoDB …
It is my pleasure to announce that Percona has acquired Tokutek and will take over development and support for TokuDB® and TokuMX™ as well as the revolutionary Fractal Tree® indexing technology that enables those products to deliver improved performance, reliability and compression for modern Big Data applications.
At Percona we have been working with the Tokutek team since 2009, helping to improve performance and scalability. The TokuDB storage engine has been available for Percona Server for about a year, so joining forces is quite a natural step for us.
Fractal Tree indexing technology—developed by years of data science research at MIT, Stony Brook University and Rutgers University—is the new generation data structure which, for many workloads, leapfrogs traditional B-tree technology which was invented in 1972 (over 40 years ago!). It is also often …
[Read more]
One of my goals at Acmebenchmarking is make sure I'm running on
hardware that is representative of real-world infrastructure,
while at the same time doing it as inexpensively as
possible.
To date I've been running on two custom built "desktops" (for
lack of a better term). Both have an Intel Core i7 4790K
processor (quad core plus hyperthreading, 4Ghz), 32GB RAM (dual
channel), and a quality SSD. They are named acmebench01 and
acmebench02.
Alas, it is time to expand.
MUST...PURCHASE...MORE...HARDWARE!
In order to maintain the inexpensive theme I tend to buy used
hardware, my goal on this purchase was to achieve many more cores
and greater memory bandwidth than my existing machines can
provide. Keep in mind that used hardware is great for
benchmarking (and likely development and QA environments) but you
might want to avoid it for production. For years now I've been
purchasing used hardware …
