MySQL 5.4 comes with Innodb engine which seems to have much better performance than MySQL 5.0 - this is due to locking and IO patches from Google integrated in this release (which are similar to appropriate Percona patches) as well as some unique fixes such as different innodb_thread_concurrency handling and other optimization.

Should we take Innodb from MySQL 5.4 and merry it with unique Percona patches (adaptive checkpoints, additional undo slots, profiling, etc) and integrate it with MySQL 5.0 ? How useful would you find it ?

Currently we see a lot of customers not quite ready to update to MySQL 5.1 in particular as there is little in this version which benefits their workload, which consists of the queries running just fine on 5.0.
5.4 especially introduces optimizer changes which besides positive impact for some queries may break something which works well now.

In general I find the current situation with Innodb is quite strange - leaving apart Innodb derivatives, like XtraDB there are 3 innodb versions around. There is MySQL 5.0 version which did not get significant changes for around 2 years now. There is Innodb Plugin which has significant architectural changes such as new storage format, compression and fast index build. Innodb plugin 1.0.3 got some Google changes for CPU scalability but not IO patches. I expected Innodb to announce plugin is now stable at users conference and may be release the version with complete set of changes from google but instead we get MySQL 5.4 release with yet another set of Innodb changes. Why not to include plugin in MySQL 5.4 with relevant performance changes instead ? This would highlight it status as future Innodb code base.

Now I’m confused - if Innodb Plugin is not taking place of default Innodb in MySQL 5.4 will this ever going to happen ?

Looking at initial benchmarks I’m very impressed with Sun Performance Team work though it looks like there was not a lot of cooperation with Innodb team (otherwise I’d expect plugin to have same codebase). I also do not think development was done in true open source spirit - trading making a big marketing splash for true openness.

Where does this leave XtraDB ? The new MySQL 5.4 release is faster than XtraDB in some workloads and this is great. Competition makes the blood move and keep developer excited. We will look into the changes and adopt the best to XtraDB.

---

Entry posted by peter | One comment

Add to: | | | |

For the past few months, more and more Analytics users have been invited to integrate their Analytics and AdSense accounts. Today that feature has become available to everyone. That means if you have an AdSense account, it's time to get it linked! Here's how:

Linking your Analytics and AdSense Accounts

1. Log in to AdSense
2. Click the link that says "Integrate your AdSense account with Google Analytics" on the Reports > Overview tab
   
3. Follow the on-screen instructions

Having trouble? Visit this help center article.


Which Reports are Available

Once you link your accounts, you'll find an AdSense-specific menu under the "Content" section of Analytics containing these reports:

• The Top AdSense Content report allows you to see more details about specific pages on your site and analyze ad performance. For instance, if you find that some of your pages generate a high number of pageviews but aren't monetizing as well as other pages, you can focus your optimization efforts on improving these pages.
  
• The Top AdSense Referrers report can help you see how different incoming traffic sources contribute to your revenue.
  
• Last, the AdSense Trending report lets you analyze how your site generates revenue during different times of the day and different days of the week.

How to Read the Reports

Check out this video to get a better understanding of how to use these reports:



You'll also notice that other sections of your Analytics account will show a new "AdSense Revenue" tab. You'll be able to compare how much of your AdSense revenue is coming from new visitors versus existing ones, and view revenue based on user language.

Enjoy your new data, and be sure to visit the Help Center if you have other questions about linking your accounts or reviewing your reports.

Like the new feature? Hate it? Leave a comment and let us know!

Posted by Sebastian Tonkin, Google Analytics Team

We announce next beta version of our xtrabackup tool.

Changelist includes:

- set innodb_fast_shutdown=1 on xtrabackup shutdown
- set innodb_write_io_threads=10 by default for fast buffer_pool flushing during recovery
- build xtrabackup with –with-extra-charsets=complex
Bug #357653: innobackupex-1.5.1 –copy-back fails
Bug #358194: 2nd-phase is very slow
Bug #358266: xtrabackup-0.5 dies with SEGV on bad command line arguments
Bug #359341: innobackupex still does not read defaults-file

You can download current binaries RPM for RHEL4 and RHEL5 (compatible with CentOS also), DEB for Debian/Ubuntu and tar.gz for Mac OS / Intel 64bit there:
http://www.percona.com/mysql/xtrabackup/0.6/.
By the same link you can find general .tar.gz with binaries which can be run on any modern Linux distribution.
By the same link you can download source code if you do not want to deal with bazaar and Launchpad.

The project lives on Launchpad : https://launchpad.net/percona-xtrabackup and you can report bug to Launchpad bug system:
https://launchpad.net/percona-xtrabackup/+filebug. The documentation is available on our Wiki

For general questions use our Pecona-discussions group, and for development question Percona-dev group.

For support, commercial and sponsorship inquiries contact Percona

---

Entry posted by Vadim | 3 comments

Add to: | | | |

+1在网上被使用的频率越来越高，今天在某个论坛看到有人提到+1的来历，说是来自日本的社区，作为万年愤青的我不由地小躯一震。于是我回想了一下，这个+1我最早应该是某个自由软件/开源社区的邮件列表里看到的。包括PHP，Apache基金会在内的很多邮件列表都是使用+1/-1这样的方式来投票。(当然，在一般的论坛里，+1/-1更多地是用来简单地表示赞同，并非是参与到某个决定/请求的投票里)

回忆结束，立马跑去wikipedia找相关条目，看到在+1条目下有一句话：“A way of voting on mailing lists and forums, used by the Apache Software Foundation and other open source organizations. By extension, a way to signify “yes” or agreement (often with a quoted post) on internet forums and similar media.”。果然是和开源社区有密切的关系阿，特别是apache基金会。

看完wikipedia，接着用voting，plus 1，mailing list之类的关键词google来google去，结果只在apache基金会找到了专门的相关文档（http://www.apache.org/foundation/voting.html）。上面还提到了两种主要的voting。一种叫lazy consensus，这种voting，就是如果在规定时间内没人投票，那么由发起投票的人做决定了。另外一种叫Majority Approval。这个的规定是需要至少3个+1，并且+1大于-1。

我还发现除了wikipedia里指名道姓是used by the Apache..之外，有一些项目的组织也提到了这个方式是取自Apache的。例如这个fluid项目的voting页面，里面就提到“The inspiration for the Fluid community’s governance process comes from the Apache Project. In the spirit of not wanting to reinvent the wheel, we have adopted Apache’s voting process, refining it a bit along the way.”。

嗯，这样看来，+1很有可能是从Apache传播开的。当然，有可能不是他们首创，而且很有可能+1这种方式在互联网没诞生前就诞生了。至于为什么近期会在国内的社区流行呢？我YY了一下，大概是自由软件的精神已经深入民心了。特别是像豆瓣这样的社区，里面类似我这种常年混迹于开源社区的小青年是何其地多阿。别的学不会，这种很方便地表达自己意愿的小玩意，还是可以学会的。

---

相关文章：

1. Zend Framework 1.0.0正式发布
2. 女性PHP程序员们冒个泡