Showing entries 1861 to 1870 of 22259
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: MySQL (reset)
How to Run Orchestrator on FreeBSD

In this post, I am going to show you how to run Orchestrator on FreeBSD. The instructions have been tested in FreeBSD 11.3 but the general steps should apply to other versions as well.

At the time of this writing, Orchestrator doesn’t provide FreeBSD binaries, so we will need to compile it.

Preparing the Environment

The first step is to install the prerequisites. Let’s start by installing git:

[vagrant@freebsd ~]$ sudo pkg update
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Fetching packagesite.txz: 100% 6 MiB 492.3kB/s 00:13
Processing entries: 100%
FreeBSD repository update completed. 31526 packages processed.
All repositories are up to date.

[vagrant@freebsd ~]$ sudo pkg install git
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
New …
[Read more]
MySQL 8.0.19 New Features Summary

Presentation of some of the new features of MySQL 8.0.19 released on January 13, 2020.

The post MySQL 8.0.19 New Features Summary first appeared on dasini.net - Diary of a MySQL expert.

MySQL Adventures: CPU Cores and IOPS on GCE

TL;DR — If you are hosting your database server in GCE, then you have to be very cautious with capacity planning. The number of CPU cores has an impact on IOPS you get. Even if your workload is not CPU intensive, you might want to provision enough depending on the kind of IOPS you are going to need. For more details, read through one of the problems we faced and the RCA.

Problem statement:

We had a master-slave setup for one of the MySQL database servers. The MySQL server’s performance was good, we didn’t notice any performance related issues initially. But we recently noticed replication lag on the slave. and we figured out that the slave thread was very slow.

Server’s Capacity:

Both our master-slave servers are of the same size.

  • 4 Core CPU
  • 16GB Memory
  • 2 databases are hosted
  • 20GB is the database size.
[Read more]
Introduction to MySQL 8.0 Recursive Common Table Expression (Part 2)

This is the second part of a two-articles series. In the first part, we introduced the Common Table Expression (CTE), a new feature available on MySQL 8.0 as well as Percona Server for MySQL 8.0. In this article, we’ll present the Recursive Common Table Expression. SQL is generally poor at recursive structures, but it is now possible on MySQL to write recursive queries. Before MySQL 8.0, recursion was possible only by creating stored routines.

What is a Recursive Common Table Expression?

A recursive CTE is one having a subquery that refers to its own name. It is particularly useful in the following cases:

  • To generate series
  • Hierarchical or tree-structured data traversal
[Read more]
preFOSDEM MySQL Days: summary and slides

What a great event ! I got very positive feedback for this extended preFOSDEM MySQL Day 2020.

Before my summary, I wanted to thank again all speakers and attendees. Without you this event won’t even exist. And thank you to ICAB for hosting us yet another time !

As you may know, we had 2 parallel tracks for 2 consecutive days. We had very valuable technical content from the MySQL developers and also from the external community members who talked about their favorite database.

There was a large interest in MySQL NDB Cluster and it was obvious that the nice presentations we had, encouraged people to try the worlds highest performance open source in-memory database (and they can even test it on their laptop with DBDeployer). The NDB users were also happy with the new stuff and impressive numbers that Bernd

[Read more]
NDB Cluster, the World's Fastest Key-Value Store

Using numbers produced already with MySQL Cluster 7.6.10 we have
shown that NDB Cluster is the world's fastest Key-Value store using
the Yahoo Cloud Serving Benchmark (YCSB) Workload A.

Presentation at Slideshare.net.

We reached 1.4M operations using 2 Data Nodes and 2.8M operations
using a 4 Data Node setup. All this using a standard JDBC driver.
Obviously using a specialised ClusterJ client will improve performance
further. These benchmarks was executed by Bernd Ocklin.

The benchmark was executed in the Oracle Cloud. Each Data Node used
a Bare Metal Server using DenseIO which have 52 CPU cores with
8 NVMe drives.

The MySQL Servers and Benchmark clients was executed on Bare Metal
servers with 2 MySQL Server per server (1 MySQL Server per …

[Read more]
MySQL Day – the Uber Experience

Last week, we had two exceptional preFOSDEM MySQL Days in Brussels. A lot of MySQL Engineers presented their work but also different MySQL Users. I will publish soon an overview of the two days, but today let me share with you an interview I did with Giedrius Jaraminas, engineering manager of MySQL team in Uber.

MySQL is heart of the Uber infrastructure“, this is how Giedrius started his presentation “Group Replication in Uber“.

The interview:

Q1: Tell us about yourself, and your experience with  MySQL

A1:  I am a database guy for 28 years, but I am relatively new to MySQL – I am a manager of MySQL team for only 3.5 years.

Q2:  Tell us about your company, and how MySQL is used.

A2:  MySQL is the main offer as a relational database, also – it is used as the …

[Read more]
Introduction to MySQL 8.0 Common Table Expressions (Part 1)

This blog is the first part of a two-articles series. In this article, I’m going to introduce the Common Table Expression (CTE), a new feature available on MySQL 8.0, as well as Percona Server for MySQL 8.

What is a Common Table Expression?

We can define a CTE as an alternative to a derived table. In a small way, CTE simplifies complex joins and subqueries, improving the readability of the queries. CTE is part of ANSI SQL 99 and was introduced in MySQL 8.0.1. The same feature is available even on Percona Server for MySQL 8.0.

The main reasons for using CTE are:

  • Better readability of the queries
  • Can be referenced multiple times in the same query
  • Improved performance
  • A valid alternative to a VIEW, if your user cannot create VIEWs
  • Easier chaining of multiple CTE …
[Read more]
Watch: Lessons from Working with NoSQL in a SQL DB & MySQL JSON Data Type Migration

Wix Engineering’s meetups focus on deep technical insights, whether it’s front-end, back-end, mobile, testing or anything in between. You can join us on Tel-Aviv, Kyiv, Dnipro and Vilnius.

Below you’ll find videos from one of our recent meetups, where our Baruch Assif Osoveksiy and Lior Altarescu, shared their work with NoSQL in a SQL Database, and MySQL JSON Data Type and Migration.

Working with NoSQL in a SQL Database (XDevApi) / Lior Altarescu

The X Dev API is a new protocol for non-blocking, asynchronous calls to MySQL.

In this talk, Lior explores the benefits of working with this …

[Read more]
MySQL Table can have the WASTED/FRAGMENTED space without data deletion ( DELETE ) ?
  • Are thinking the table fragmentation will be happened with only DELETE’s ?
  • Do you believe the INSERT’s will also cause the table fragmentation ?

Yes, INSERT’s with the ROLLBACK can also create the table fragmentation . In this blog I am going to explain how the INSERT is causing the table fragmentation .

How the table fragmentations is happening with INSERT and ROLLBACK ?

When you triggered the INSERT, it will start to write the data into it’s table space file ( .ibd ) . Right ?

From the snap, I have created the table and started the transaction ( BEGIN ) with INSERT . Within the transaction the INSERT has been completed but still I did not commit / rollback the transaction .

You can check the table space file growth to 1.2 GB .

Now, I am going to rollback the transaction .

After the ROLLBACK completed, still the …

[Read more]
Showing entries 1861 to 1870 of 22259
« 10 Newer Entries | 10 Older Entries »