Google patches V1 contain interesting patch to mirror binary log on slave. Although Google is preparing GlobalTransactionId patch, which going to be replacement for MirroredBinlogs, we still think mirroring binary logs is very useful for:

• Backup of binary logs in real time
• High availability, to switch master load to slave with mirrored binary logs

By request of our friends EngineYard we extracted this patch from Google’s patchset and going to include in our next releases. Actually our patch contains features for both MirroredBinlogs and FastMasterPromotion patches, as second provides feature to make slave as master in case of main master failure.

At this moment you can download patch by itself there
http://www.percona.com/mysql/5.0.67-b6/patches/mirror_binlog.patch
with docs on our wiki

Also the patch will be included in OurDelta binaries beside our releases for CentOS / RedHat platform, so you can download and test this feature for your OS.

---

Entry posted by Vadim | No comment

Add to: | | | |

Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
Flush history file on disk (unique url reach flush limit of 5000)
Flush history file on disk (unique url reach flush limit of 5000)
Flush history file on disk (unique url reach flush limit of 5000)
是AWStats统计常见的输出，每行都是在处理完一定数量的URL(缺省是5000个)后，AWStats将统计结果临时写入磁盘。最近使用AWStats处理百M级别的日志时：磁盘IO居然非常高，
发现有时候遇到页面URL个数非常多的时候（比如：在搜索引擎蜘蛛对网站进行深度遍历deep crawl时），经常会使得AWStats对缓存文件的读写过于频繁，随着生成的数据文件越来越大，每次几百M的临时文件读写也会导致统计速度越来越慢；经常一次统计数据下来会Flush history file on disk (unique url reach flush limit of 5000) 几百次；

记得以前是对AWStats进行过简单的参数配置的，可以修改flush的周期，但现在的文档中没有找到相应的配置，只好Hack了一下：awstats.pl文件将每隔发现5千个新链接改为5万个；

> $LIMITFLUSH=5000; # Nb of records in data arrays after how we need to flush data on disk
---
< $LIMITFLUSH=50000; # Nb of records in data arrays after how we need to flush data on disk

其实内存够用的话，将这个值设置的更高也是没有问题的。根据观察临时文件生成的次数也相应的有数量级的下降；这个参数和Lucene中的merge_factor有点像，都是拿内存换速度；

Have you seen the getting-prettier-all-the-time menus in 2.7-almost-beta? They really are. Getting prettier all the time, I mean. Once we drop in the fonts and do a little brushing up of edges and colors, the menu system is going to be smooth. The last thing we’ll need to do to is replace the icons we’ve been using as placeholders. Currently, the menus are using icons from Crystal Project, which is perfect because they’re released under LGPL (yay for open source!), but less perfect in that they don’t quite fit with the new visual style of 2.7, so we’re thinking custom icons.

I’m always meeting people at WordCamps or via email who say they wish they could give back to WordPress, but that since they aren’t PHP developers, they feel like there isn’t any opportunity for them to be a part of the open source project. Well, here’s a golden opportunity. Want to design the new WordPress icons?

The icons:
We’ll need icons for each of the main navigation sections, plus a matching pair of list/excerpt view icons for the table screens like Edit Posts. That’s a total of 13, and for the navigation icons we’ll also need a larger size for use in the screen headers. Some of the sections have natural iconography, while others may be more challenging. The sections are: Dashboard, Posts, Media, Links, Pages, Comments, Appearance, Settings, Users, Plugins, Tools.

The style:
Icons should be subtle, with a classic/designed look, nothing cartoonish. Thin lines. Maybe a little old-fashioned looking. They’ll be grayscale by default, possibly with a color version for active menu items.

The timing:
Fast, fast, fast. 2.7 is due to release on November 10. That means icons need to be ready within two weeks, give or take.

The required experience:
To be taken seriously, you’ll need to show a background in icon design. It’s a different skill than web site or application design, and given that there’s not much time before the 2.7 launch, someone with experience (and possibly existing work they can leverage) is going to be the best candidate.

Interested? Send us an email and tell us why you want to design the icons, and include a link to your portfolio. How we wind up choosing an icon designer will depend on how many people respond, but we’ll keep you posted on the process. For now, send in portfolio links by Saturday night, October 25, 2008. We’ll review them over the weekend and get in touch with people on Monday. Hopefully we can be designing by early next week.