Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
10 Newer Entries Showing entries 61 to 70 of 116 10 Older Entries

Displaying posts with tag: newsql (reset)

Webinar: Introduction to TokuDB
+1 Vote Up -0Vote Down

Businesses increasingly operate in a 24×7 environment, where complex analytics must be performed on live, continuously incoming “Big Data.” To address this, TokuDB has developed Fractal Tree®  technology, a revolutionary new indexing capability that enables SQL databases running advanced web applications to grow from gigabytes to terabytes while improving insert speed, query performance, compression, and enabling zero-downtime schema changes.

Date: September 5th
Time: 2 PM EST / 11 AM PST

REGISTER TODAY

TokuDB is used by MySQL and MariaDB customers worldwide to increase their database performance by 20x-80x on Big Data applications that conventional RDBMS’s cannot handle. Instead


  [Read more...]
Dagstuhl Seminar on Database Workload Management
+1 Vote Up -0Vote Down

A few weeks ago Bradley Kuszmaul and I attended the Dagstuhl Seminar on Database Workload Management.

The Dagstuhl computer science research center is (remotely) located in the countryside in Saarland, Germany. The actual building is an 18th Century Manor House, first retooled as an old-age home, and then a computer science research center. Workshop participants typically spend the whole week talking and working together.

Dagstuhl Computer Science Center

Shivnath Babu (Duke University), Goetz Graefe (Hewlett Packard),

  [Read more...]
Real World Compression
+1 Vote Up -0Vote Down

Benchmarking is a tricky thing, especially when it comes to compression. Some data compresses quite well while other data does not compress at all. Storing jpeg images in a BLOB column produces 0% compression, but storing the string “AAAAAAAAAAAAAAAAAAAA” in a VARCHAR(20) column produces extremely high (and unrealistic) compression numbers.

This week I was assisting a TokuDB customer understand the insertion performance of TokuDB versus InnoDB and MyISAM for their actual data. The table contained a single VARCHAR(50), multiple INTEGER, one SET, one DECIMAL, and a surrogate primary key.  To support a varied query workload they needed 6 indexes.

Here is an obfuscated schema of the table:

col1 varchar(50) NOT NULL,
col2 int(40) NOT NULL DEFAULT '0',
col3 int(10) NOT NULL DEFAULT '0',
col4 int(10) NOT NULL DEFAULT '0',
col5 int(10) NOT NULL DEFAULT '0',
col6
  [Read more...]
Thursday’s Emerging Business Technology Meetup in Boston
+0 Vote Up -0Vote Down

I’ll be presenting TokuDB at the Emerging Business Technology Meetup in Boston this Thursday night at 6pm at 290 Congress St (near South Station).  The meeting topic is “NewSQL: SQL Technologies Keeping NoSQL Promises” and also includes presentations from Akiban and VoltDB.  Each of us will be highlighting our technology and use-cases, with a panel discussion and open Q&A to follow.

This is a well attended group with 102 currently registered for the meeting and room for 48 more.  If you

  [Read more...]
Webinar: Understanding Indexing
+1 Vote Up -0Vote Down

Three rules on making indexes around queries to provide good performance

Application performance often depends on how fast a query can respond and query performance almost always depends on good indexing. So one of the quickest and least expensive ways to increase application performance is to optimize the indexes. This talk presents three simple and effective rules on how to construct indexes around queries that result in good performance.


Time: 2PM EDT / 11AM PDT

This webinar is a general discussion applicable to all databases using indexes and is not specific to any particular MySQL® storage engine


  [Read more...]
Announcing TokuDB v6.1
+3 Vote Up -0Vote Down

TokuDB v6.1 is now generally available and can be downloaded here.

New features include:

  • Added support for MariaDB 5.5 (5.5.25)
    • The TokuDB storage engine is now available with all the additional functionality of MariaDB 5.5.
  • Added HCAD support to our MySQL 5.5 version (5.5.24)
    • Hot column addition/deletion was present in TokuDB v6.0 for MySQL 5.1 and MariaDB 5.2, but not in MySQL 5.5.  This feature is now present in all MySQL and MariaDB versions of TokuDB.
  • Improved in-memory point query performance via lock/latch refinement
    • TokuDB has always been a great performer on range scans and workloads where the size of the working data set is significantly larger than RAM.  TokuDB v6.0 improved the performance of in-memory point queries at
  [Read more...]
How We Spent a Tuesday Fixing a MySQL Replication Bug
+3 Vote Up -0Vote Down

We found a simple XA transaction that crashes MySQL 5.5 replication. This simple transaction inserts a row into an InnoDB table and a TokuDB table. The bug was caused by a flaw in the logging code exposed by the transaction’s use of two XA storage engines (TokuDB and InnoDB). This bug was fixed in the TokuDB 6.0.1 release.

Here are some details.  Suppose that a database contains the following tables.

create table t1 (a int) engine=InnoDB
create table t2 (a int) engine=TokuDB

 The following transaction

begin
insert into t1 values (1)
insert into t2 values (2)
commit

causes the replication slave to crash.

The crash occurs when mysqld tries to dereference a NULL pointer.

#4  0x000000000088e203 in MYSQL_BIN_LOG::log_and_order (this=0x14b8640, thd=0x7f7758000af0, xid=161, all=true,





  [Read more...]
My Talks at MySQL Connect and Percona Live NYC
+1 Vote Up -0Vote Down


Solving the Challenges of Big Databases with MySQL

When you’re using MySQL for big data (more than ten times as large as main memory), these challenges often arise: loading data fast; maintaining indexes under insertions deletions, and updates; adding and removing columns online; adding indexes online; preventing slave lag; and compressing data effectively.

This session shows why some of these challenges are difficult to solve with storage engines based on B-trees, how Fractal Tree® data structures work, and why they can help solve these problems. Tokutek sells a transaction-safe Fractal Tree storage engine for MySQL, but the presentation is primarily about the underlying technology. It includes a discussion of both the theoretical and practical aspects of Fractal Tree indexes.

I have the privilege of being able to give


  [Read more...]
Balada Para Un Loco – A Review of the MySQL, NoSQL, and Cloud Conference
+1 Vote Up -0Vote Down

… Ya se que estás piantao, piantao, piantao…

For my lastest blog, a review of the MySQL, NoSQL and Cloud Conference, I’ll continue to use the tango metaphor. Balada para un loco (ballad for a crazy one) is a Piazzola classic and explains what I think of Santiago Lertora from Binlogic for single handedly putting together this event; he had to be piantao (slang for ‘crazy’) to pursue his vision to kick start the Open Source database community in South America into becoming as active as it is in the US and Europe. He was able to gather some renowned speakers such as our own Martin Farach-Colton, Sheeri Cabral from Mozilla, Max Mether and Massimo Brignoli from SkySQL, Colin Charles from Monty Program, Alejandro Kojima

  [Read more...]
How to Stop Playing “Hop and Seek”: MySQL Cluster and TokuDB, Part 2
+1 Vote Up -0Vote Down

In my last post, I wrote that I observed many similarities between TokuDB and MySQL Cluster. Many features that benefit TokuDB also benefit MySQL Cluster, and vice versa, with Hot Column Addition and Deletion (HCAD) being an example. Over my next few posts, I expand on some more of these possibly unexpected similarities.

Today I want to focus on optimizer support for clustering keys. Both MySQL Cluster and TokuDB can benefit from the MySQL optimizer supporting clustering keys. For TokuDB, the

  [Read more...]
10 Newer Entries Showing entries 61 to 70 of 116 10 Older Entries

Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.