18 April 2014

The Ruby Reflector

Topic

Peter Zaitsev

  Source Favicon
Email

…afternoon of talks and sharing of best practices for both technologies. After a brief welcome message from Peter Zaitsev, co-founder and CEO of Percona, Florian Haas shared an introduction to OpenStack including its history and the basics of how it works.

Jay Pipes delivered lessons from the field based on his years of OpenStack experience at AT&T, at Mirantis, and as a frequent code contributor to the project. Jay Janssen , a Percona managing consultant, complemented …

mysqlperformanceblog.com Read
  Source Favicon
By Peter Zaitsev of MySQL Performance Blog 3 days ago.
Email

Other the last few days, the Percona team has spent a lot of time evaluating the impact of the Heartbleed bug ( CVE-2014-0160) for our customers and for the users of our software. We published a formal disclosure a few days ago. However, I thought a quick summary and some additional information would be good to provide for our MySQL Performance Blog readers.

First, I want to point out that " Heartbleed" is an issue in a commonly used third-party library which typically …

mysqlperformanceblog.com Read
  Source Favicon
Email
  Source Favicon
By Peter Zaitsev of MySQL Performance Blog 24 days ago.
Email

I'm looking forward to Wednesday's joint webinar on MySQL clustering technologies with Matt Aslett, research director of data management and analytics over at 451 Research. We'll be participating in a live, in-depth discussion of MySQL Clustering for High Availability and Scalability.

Matt will present an overview of the trends driving adoption of clustering technology. He'll also discuss the key technologies and criteria that developers and administrators …

mysqlperformanceblog.com Read
  Source Favicon
Email

Continuent's Robert Hodges, and Percona's Peter Zaitsev. This year we will also feature a keynote panel on "The Future of Operating MySQL at Scale". I will host the panel which features Robert Hodges, Nisha Talagala, and Peter Zaitsev, and will focus on the challenges of operating MySQL at scale when downtime is very costly for mission-critical applications and more and more companies running MySQL in the Cloud. We will discuss topics such as high availability …

mysqlperformanceblog.com Read
  Source Favicon
Email

…this nice blogpost from my colleague Roman. Further, our CEO Peter Zaitsev also wrote a post recently where he shows the comparison between performance_schema and slow query log. Check here for details.

In related new, Percona recently announced Percona Cloud Tools , the next generation of tools for MySQL. It runs a client-side agent (pt-agent) which runs pt-query-digest on the server with some intervals and uploads the aggregated data to the Percona Cloud Tools API…

mysqlperformanceblog.com Read
  Source Favicon
By Peter Zaitsev of MySQL Performance Blog 1 month ago.
Email

Monitoring MySQL and effectively managing it can be challenging. Identifying issues before they grow into performance problems that impact end users can be crucial. Knowing which tools to use, which key metrics to monitor, and how to resolve issues can be enormously important. When considering these facts, we at Percona decided to take steps to provide our Support customers with the tools, alerts, and advice they need to have higher performing, more secure, and easier to manage MySQL deployments.

mysqlperformanceblog.com Read
  Source Favicon
Email

In fact, in a past blog post, Peter Zaitsev showed in a test that prepared statements allow for a significantly higher rate of queries per second than non-prepared queries.

I have also done tests with PHP, and I found that the overhead to response time is due more to additional PHP code than the performance on the database server side.

One more performance consequence of using prepared statements: compatibility with the query cache. If you issue SQL statements with the text …

mysqlperformanceblog.com Read
  Source Favicon
By Peter Zaitsev of MySQL Performance Blog 1 month ago.
Email

When looking at queries that are candidates for optimization I often recommend that people look at rows_sent and rows_examined values as available in the slow query log (as well as some other places). If rows_examined is by far larger than rows_sent, say 100 larger, then the query is a great candidate for optimization. Optimization could be as simple as adding a few indexes or much more complicated as in generating summary tables so you do not need to rely on large aggregations for your real-time queries.

mysqlperformanceblog.com Read
  Source Favicon
By Peter Zaitsev of MySQL Performance Blog 2 months ago.
Email

A couple of weeks ago, shortly after Vadim wrote about Percona Cloud Tools and using Slow Query Log to capture the data, Mark Leith asked why don't we just use Performance Schema instead? This is an interesting question and I think it deserves its own blog post to talk about.

First, I would say main reason for using Slow Query Log is compatibility. Basic Slow query log with microsecond query time precision is available starting in MySQL 5.1, while …

mysqlperformanceblog.com Read