Yii is a high-performance framework. The graph below shows how efficient Yii is when compared with other popular PHP frameworks. In the graph, RPS stands for "request per second" which describes how many requests an application written in a framework can process per second. The higher the number, the more efficient a framework is. As we can see that Yii outperforms all other frameworks in this comparison. The performance advantage of Yii is especially significant when the widely used APC extension is enabled.

同城上线一年了，首页有很多不方便使用的地方，是时候修改啦。新版首页近日上线，做了如下改进。
 
一周热门得到突出
新首页突出了一周热门模块，并增加了分类型显示。除了所有活动中最热门的内容外，你还可以轻松浏览活动总数最多的其他类型，诸如“音乐演出”“生活聚会”等。

更方便的过滤器
旧版的时间选择在上方，内容选择则放在左侧，如果我想查找“今日的音乐演出”，操作会很不方便。新版将时间和内容类型放在同侧，并且给了交叉选择非常清晰的高亮。在不同类型之间的切换也非常容易。

主题活动
新版同城以后会出现主题活动啦。在每个我们准备热热闹闹用活动庆祝的情人节、儿童节、中秋节、音乐季、戏剧节……主题活动都会出现。它们仍然是豆子们自己创建的活动，只不过后台用主题索引了一下，将它们集中展示在首页模块里。月底的地球日不知道有多少环保分子会来同城找活动呢？
 
精彩回顾
老版首页没有已结束活动的一席之地。很多积累了精彩照片和讨论的活动都愤愤不平。其实结束的活动也有很大的资料价值（展览的照片能让没去的人大饱眼福）。看见自己辛苦组织的活动出现在“精彩回顾”里，发起人也应该很高兴吧。
 
说了这么多，还是希望新首页能让大家用得更方便。无论是迎来的是砖头还是花瓣，让我们先期待它上线吧。

Are you using someone else’s backup solution for your MySQL data? Do you care a lot about your data? Are you sure you’re getting a reliable, recoverable backup that’ll work for your business and your application, and won’t impact your critical processes while it runs? Here are ten questions you need to be able to answer:

1. Does the backup require shutting down MySQL? If not, what is the impact on the running server? Blocking, I/O load, cache pollution, etc?
2. What technique is used for the backup? Is it mysqldump or a custom product that does something similar? Is it a filesystem copy?
3. Does the backup system understand that you cannot back up InnoDB by simply copying its files?
4. Does the backup use FLUSH TABLES, LOCK TABLES, or FLUSH TABLES WITH READ LOCK? These all interrupt processing.
5. What other effects are there on MySQL? I’ve seen systems that do a RESET MASTER, which immediately breaks replication. Are there any FLUSH commands at all, like FLUSH LOGS?
6. How does the system guarantee that you can perform point-in-time recovery?
7. How does the system guarantee consistency with the binary log, InnoDB logs, and replication?
8. Can you use the system to set up new MySQL replication slaves? How?
9. Does the system verify that the backup is restorable, e.g. does it run InnoDB recovery before declaring success?
10. Does anyone stand behind it with support, and guarantee working, recoverable backups? How strong is the legal guarantee of this and how much insurance do they have?

There are a lot of other things a backup solution needs to provide, but these are some of the things I’d require specifically for MySQL, or more so for MySQL than for other types of backups.

Where is this post coming from? Well, I’ve had a couple of frustrating encounters with vendors who sell backup products with some kind of agent for MySQL backup. I am almost never able to get any significant technical detail on how their backups are implemented, and often I can’t even get the most basic information such as “dump or file copy.” Sometimes they tell me to register and download a whitepaper that just has a bullet point “Support for MySQL Databases”. Or “I have to transfer you to the salesperson who covers your region” and I never get to talk to anyone.

Some of them even use the word “proprietary” as if it’s a good thing. In reality, a proprietary, secret backup black-box is unacceptable. MySQL backups are complex and difficult to get right. It is very application-dependent and technology-dependent. Unless I know exactly how it works, I cannot tell the client whether it’ll work for them at all.

So I offer the above list as a way to evaluate your backup provider’s suitability for enterprise-ready backup uses. If you can’t answer these questions, it’s a system that you can’t evaluate seriously, in my opinion.

---

Entry posted by Baron Schwartz | 3 comments

Add to: | | | |