In my previous blog post, I discussed the enhanced performance and scalability delivered by extensions to the multi-threaded data nodes in MySQL Cluster 7.2. In this post, I’ll share best practices on the configuration of data nodes to achieve optimum performance on the latest generations of multi-core, multi-thread CPU designs.

Configuring the Data Nodes

The configuration of data node threads can be managed in two ways via the config.ini file:

- Simply set MaxNoOfExecutionThreads to the appropriate number of threads to be run in the data node, based on the number of threads presented by the processors used in the host or VM.

- Use the new ThreadConfig variable that enables users to configure both the number of each thread type to use and …

Technical blogging has become more than just a way to tell the world what the technologist did. It has become a vibrant medium through which the tech bloggers are sharing their experiences and teaching the interested audience. It has become an enabling technology. This Log Buffer Edition encompasses such vibrant blogs in Log Buffer #274. [...]

The best (and truly the only) MySQL multi-master, multi-site solution on the market gets even better! Continuent is happy to announce immediate availability of Continuent Tungsten 1.5.New Continuent Tungsten 1.5 allows you to build multi-site, disaster recovery (DR) and multi-master solutions with ease:

Multi-Master Operations - Tungsten can support your multi-master operations today by linking

JSON is a data format that has become very popular recently. The name JSON means "JavaScript Object Notation" and it's a bit misleading, as although the format originally was used in JavaScript, it has become very popular in many more environments.

JSON is used as a format of both queries and results in database applications, as well as for data export and import. Among the most JSON centric database system, and also the most JavaScript focus one I guess, is MongoDB. In the world of NoSQL, JSON is used extensively, as JSON is really cool for representing documents and stuff like, and for a variety of other reasons too. JSON is a format that is also textual and easy to read, and the format is pretty standardized.

Drizzle has some features for working JSON, and this is a pretty good example of something that is becoming real common: REST + JSON, so a standard HTTP call using JSON for input and output. There …

Yesterday, it was announced that SkySQL has raised an additional 2.5 million dollars in Series A funding from California Technology Ventures.

This comes along with the news of the new CEO, Patrik Sallner, taking the CEO role at SkySQL on July 1st.

Here are some relevant snippets:

“SkySQL also announced today that CTV, a venture capital fund that makes direct investments in technology and life science companies globally, invested an additional $2.5 million as part of the company’s recent A round of funding. With this latest investment, SkySQL has collected EUR 6 million to fund further growth.”

“About California Technology Ventures, LLC
California Technology Ventures, LLC is a venture capital fund that makes direct investments in technology and life science companies. CTV has built a strong reputation for its entrepreneurial approach to investing and working with companies. They believe in guiding …

In case you may have overlooked yesterday’s post from Ulf Sandberg, I thought I’d go ahead and reiterate the main points, as it is big news, at least for those interested in SkySQL.

SkySQL has been like a rocket ship with it’s growth since we started, and now we’re making some even bigger changes to help accelerate that effort further.

As Ulf announced, we’ve named a new CEO, Patrik Sallner, to take over after the initial bootstrap period.

Patrik, a former executive at F-Secure, will officially become CEO on July 1st. “Patrik comes to SkySQL with demonstrated experience in building international software and services businesses, including delivering cloud storage solutions to the world’s largest telecommunications operators. The addition of Patrik to SkySQL’s Leadership Team is a tremendous boon to …

MySQL developers will cover upcoming features.   The MySQL engineering team is driving MySQL forward and users feedback is welcomed. For those having tested the Development Milestone releases this is a good opportunity to share your feedback and ideas.

The agenda includes :

InnoDB online operations Replication : Global transaction IDs for replication and failover Multi-Threaded [...]

This is the third blog post in the series of blog posts leading up to the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. This blog post is targeted at the join related optimizations introduced in the optimizer. These optimizations are available in both MySQL 5.6 and MariaDB 5.5, and MariaDB 5.5

The post Join Optimizations in MySQL 5.6 and MariaDB 5.5 appeared first on ovais.tariq.

Do the operating systems kill your MySQL instances from time to time? Are some database servers swapping constantly? These are relatively common problems. Why? How to prevent them?

Memory allocation

When a running program needs some additional memory, it can typically allocate it dynamically with malloc() function. It finds an unused continuous block that is at least as large as the requested size, reserves as much as it needs, and returns a pointer to that space. No initialization of the memory contents is performed at the time. When malloc() returns NULL instead of a valid address, it is an information to the calling program that there wasn’t enough memory available and the call has failed to allocate anything. In such cases applications typically take appropriate actions to notify users about the problem and terminate some of their activity or completely shut down.

In Linux it can be a little bit …

MariaDB 5.3/5.5 has introduced a new join type “Hash Joins” which is an implementation of a Classic Block-based Hash Join Algorithm. In this post we will see what the Hash Join is, how it works and for what types of queries would it be the right choice. I will show the results of executing benchmarks for different queries and explain the results so that you have a better understanding of when using the Hash Join will be best and when not. Although Hash Joins are available since MariaDB 5.3, but I will be running my benchmarks on the newer MariaDB 5.5.

Overview

Hash Join is a new algorithm introduced in MariaDB 5.3/5.5 that can be used for joining tables that have a equijoin conditions of the form tbl1.col1 = tbl2.col1, etc. As I mentioned above that what is actually implemented is the Classic Hash Join. But its known as Block Nested Loop Hash (BNLH) Join in MariaDB.
The Classic Hash Join Algorithm …