22:55 文本广告点击最多,越富点击广告越少 » laolu's blog: Blog

iPerceptions, Inc.10月6日披露一份研究用户对网络广告选择偏好的调查:视频广告不受欢迎,用户更倾向点击传统的文本或banner广告。调查样本是领先媒体网站的14000名访问者。

MarketingCharts以"网络文本广告点击最多,只有年轻人喜欢视频[广告](Online Text Ads Most Clicked, Only Young Like Video)"为题做了报道,主要内容有:

虽然目前对新奇昂贵的视频广告的讨论较多,但只有11%的用户说他们会点击视频广告,而有25%的人会倾向点击简单的文本广告,20%的人会点击右侧的banner广告,明显胜过顶部banner广告(12%)。视频广告总体不受欢迎,不过25岁以下的年龄组更倾向点击视频广告,超过任何其他种类广告。这个年龄组占视频广告受众的将近1/3。

第一次访问网站的人和较低收入的人,更倾向点击视频广告,而不是其他类型广告。

研究发现在收入与点击倾向之间有很强的关联。用户收入越高,越少会点击广告。平均而言,在会点击广告的用户中,有40%的年收入低于5万美元,只有15%年收入超过15万美元。收入差距在视频广告上表现得最明显,会点击视频广告的用户中,49%的人年收入低于5万美元,仅13%年收入超过15万美元。

点击次数也随着[用户对]网站忠诚度的上升而增加。在会点击网络广告的用户中,有65%的人是每周或每天浏览一个网站,仅15%是第一次访问的人,6%是偶尔访问的人。


图片来源:MarketingCharts - Online Text Ads Most Clicked, Only Young Like Video

21:58 微软,盗版,和粉丝 » Yining.write()

keso说

中国用户是有骨气的,很多出色的开源操作系统摆在我们面前,我们从来都没有正眼瞧过。我们不光热爱微软的Windows,还热爱微软的 Office,微软的IE。我们热爱微软,所以我们不给微软的竞争对手任何机会,你的产品再好,我就是不用。我们万众一心,牢牢地替微软把守着市场占有率的阵地。让Linux走开,让金山转型做游戏,让所有超越的梦想慢慢枯竭而死。不用谢我们,这都是一名粉丝应该做的。

其实,粉丝与粉丝还是不一样的,只要掌握了一小撮粉丝,所有的粉丝就会永远像现在“早已丧失了选择的能力“而“爱微软”。

还是让Steve Balmer亲自告诉大家这一群粉丝是谁吧,请看大屏幕:

Developer,软件开发者。只要他们还在开发只在Windows上运行的软件(股票客户端,图片编辑,即时通讯,在线银行服务… 所有工作的挣钱的管钱的打发时间的),那么大部分的用户还是要使用Windows不可。究其根源,与爱无关,与盗版无关,这是依赖。要让大众有更多的选择,首先就要让开发者提供相应的选择。 在大陆,很遗憾,大部分的程序员还是离不开Windows,即使开发语言是跨平台的Java,PHP等,他们还是要在Windows上编程和测试。

哦,对了,他们学习起步的教材的编纂者们,他们的老师们,恐怕也多是粉丝,而且还有言传身教盗版的粉丝

不改变软件开发者们对Windows的依赖,就算半年微软后把黑屏改成每俩小时重启一次,粉丝们的爱还是爱不完的。即使Windows最后彻底不让用了,他们也会像电影《肖申克的救赎》里的老Brooks一样,恢复自由身后,还是在墙上刻上“粉丝曾经在这里”,然后踢倒脚下的凳子,吊死自己,如Brooks的狱友,Morgan Freeman扮演的Red的一句台词:

These walls are funny. First you hate ‘em, then you get used to ‘em. Enough time passes, you get so you depend on them. That’s institutionalized.

02:09 The New 2.7 Dashboard » WordPress Development Blog

First, I’d like to say that I’m glad the majority response to the screenshots we posted last week was so positive. With a community as vocal as this one, it’s always a little nerve-wracking to introduce change, but this time it seems like the change was welcomed, which has been great. I’m hopeful that as we introduce the new features of 2.7 over the coming weeks, the good feelings will continue. As promised, here’s a rundown of what’s going to happen to the Dashboard over the next couple of weeks before launch.

Menus
I described the menu functions last week, but I forgot to mention something. By default, when you arrive at your Dashboard the first time, two sections of the navigation will be expanded: the Dashboard section (because it is active, so it will have the color highlight) and the Posts section (because it has often-accessed screens in it, and will serve as a cue that you can view other section menus without loading new screens). Once you start clicking menus open and closed, your browser will cookie you, and will remember your menu state. So if you open Posts and Comments, when you come back the next time, Posts and Comments will be open. If you click into your Settings, Posts and Comments will still be open. You’ll need to manually close nav sections. We went back and forth on this, and there was community discussion about perhaps only allowing two sections to be open at a time, but ultimately those approaches would have removed control from the user. And since the mantra of 2.7 is to give the user control over his/her admin interface, we chose to keeps things open if the user had opened them.

Contextual Access Tabs
In the upper right, drop-tabs provide access to contextual features displayed in a layer that appears between the header and the main working area. Screen Options will allow you to choose which modules to display on the current screen. Don’t like seeing the Incoming Links module because no one links to you? A simple checkbox in the Options tab will remove the module from your Dashboard until you decide to reinstate it. Help will highlight some of the changes since the previous version, and provide links to help resources such as FAQ/Forums/Contact Support for .com and Documentation/Support Forums for .org.

Module Layout
In addition to using the Options tab to decide which modules to display on the Dashboard, all the modules on the Dashboard may be moved up or down or between columns using drag and drop. Modules also may be collapsed or expanded by clicking the title bar, allowing another level of screen customization. In 2.8, we also hope to make every single module configurable in terms of what content it displays… we ran out of time for this in 2.7, so for now only the newsfeed modules will be configurable. When you hover over the module, a link will appear in the module header allowing access to the configuration view.

Right Now
The Right Now module contains the same data as before, but it’s been rearranged to provide a clearer display. This list style, as opposed to the previous sentence style, will also make translation for non-English sites easier. Color cues help to highlight things that are not good (red), things that are pending (yellow/orange), and things that are good to go (green).

Stats
I’d like to apologize for having a non-core piece of functionality on the Dashboard comp. It’s my fault… when we were working on the comps, we used my wireframes and my live 2.7 Dashboard to assemble our elements, and I forgot that I had the WordPress.com stats plugin installed and a module on my Dashboard. So even though it’s not in core and it turns out the WordPress.com stats plugin is undergoing some reworking of its own, we made the Dashboard stats module easier to scan than the one I currently see when I log in. For those of you on .org who got excited when you saw the Dashboard comp with stats, again, I apologize for the oversight on my part. If you want the candy-like stats goodness we comped up you’d need to install the plugin (or another stats plugin with candy-like elements). There should be a fine-looking Dashboard module as part of the update they release.

QuickPress
QuickPress is a new feature that provides the ability to start (or publish) a simple post from the Dashboard when you don’t need the full feature set of the Add New Post screen. Currently, these posts can contain title, text, media and tags. In 2.8 we hope to make the module configurable, so that each user can decide which few fields make the most sense to display. If you Save as Draft, you will see the new draft appear in the Recent Drafts module right away. Clicking Cancel will clear the form. Publish publishes the post. Posts made using QuickPress are the same as other posts and may be editing by going to Posts > Edit and selecting the post in question. One last thing: both in this module and on the Add New post screen, we’ve put as much space as possible between the Save Draft and Publish buttons, so for all of you who’ve asked at WordCamps or emailed or posted somewhere to request this, ta da! Hopefully this will reduce accidental publications.

Recent Drafts
During the summer testing, one thing we heard over and over was the desire to access recent drafts more easily, preferably with one click from the Dashboard (as opposed to clicking on Drafts from the Right Now module, waiting for page to load, then clicking on a specific draft title and waiting for a second page load). The Recent Drafts module is meant to address that need, displaying the five most recent drafts with the date they were created. In a future version, this module will be configurable as well. In the meantime, if you’re a crosswords-in-pen kind of person and you don’t write drafts, just use the Options tab at the top to hide the Drafts module, and it won’t take up space on your Dashboard.

Feeds
News feeds of WordPress-related news will function largely the same as they did in 2.6 in terms of configurability, and will simply have a new look. You can still specify the URL of the feed, how many items to display, whether to show headline vs excerpt, author, date, etc.

Incoming Links
Just getting a face lift. Or maybe not a face lift, more like a visit to the Clinique counter.

Hooks
Plugins can still add modules to the Dashboard. They also still can add top-level menu items if necessary (as opposed to having them in Tools, Plugins, Settings or wherever…like Posts if it’s post-specific). Because we’ll be using iconography in the collapsed menu state, plugins that create top-level menus can create an icon for use in the menu system. When there’s no icon associated with the plugin, a default will be used (kind of the way some blogs show default avatars when no Gravatar is associated with a commenter on your blog). Hopefully, though, most plugins will fit within existing section headers, since our “top level” is not actually made up of menu items, but section headers that open to reveal the real menu items that have screens associated with them. Plugins can also put themselves into the Shortcuts/Favorites menu in the header.

Recent Comments
This module, as in 2.6, displays the most recent comments. However, you now can moderate comments directly from this Dashboard module, including the new Comment Reply feature. For now it will show only the last x number of comments, as it does currently, though in 2.8 we hope to add more configurability to this, or roll it into the Inbox concept.

Bye-Bye Inbox
For those who were at WordCamp SF or who were using the nightly builds while there was still an Inbox placeholder, sorry, no Inbox in 2.7. It turned out to be far more complex than anticipated, and rather than including something rushed and clunky, we’re holding off until a later version. We added the comment moderation to the Comments module to make up for it, so you don’t have to wait for that, at least.

So that’s the new Dashboard. A little more usable, a little prettier, a little more you, a little cooler. Or maybe a lot of all those things. We’ll let you be the judge.

00:22 Improved InnoDB rw_lock patch » MySQL Performance Blog

There is patch from Google to improve SMP performance , but for some workloads it showed for us reverse scalability.
E.g. update_key benchmark from sysbench. There are also results with Yasufumi's rw_locks (http://bugs.mysql.com/bug.php?id=26442)

Threads Standard InnoDB Google smpfix Yasufumi rw_lock
1 9700.28 10601.96 9432.44
2 14355.66 16673.31 12783.58
4 16104.20 2669.39 6308.92
8 18507.55 780.22 1854.43
16 16178.09 842.73 1601.05
32 12337.50 2028.89 3274.13
64 7801.18 1911.94 4043.85

results are in tps, more are better

(result in tps, more is better)
The benchmark was made on 8cores box, and as you see for 4+ threads we have worse results than for 2 threads. That is was main reason why we did not include InnoDB smp fixes in our build yet.

Fortunately we get fixed version of Yasufumu's rw_locks and you can download them there

The results for the same benchmark:

Threads Standard InnoDB Yasufumi rw_lock ver 2
1 9700.28 9812.18
2 14355.66 14602.46
4 16104.20 18726.22
8 18507.55 19099.80
16 16178.09 17470.22
32 12337.50 12407.24
64 7801.18 7669.73

And for other workloads new rw_locks show results comparable with Google's smpfix, so we will include
innodb_rw_lock into our next -percona-highperf release


Entry posted by Vadim | No comment

Add to: delicious | digg | reddit | netscape | Google Bookmarks


^==Back Home: www.chedong.com

^==Back Digest Home: www.chedong.com/digest/

<== 2008-10-20
  十月 2008  
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
==> 2008-10-22