20:42 感谢论坛的“超级用户” » 谷歌中文网站管理员博客
发表者: 马婞, 搜索质量组

谷歌中文网站管理员支持论坛是在2009 年3 月正式搬到了这个新的平台上。在过去的三个月里,我们很高兴地看到很多原来论坛上的老朋友,和来自各地的新朋友在这里重新注册。目前我们已经有将近1500名用户,和十几名“二级”以上的用户。

在这个过程中有很多用户给予了我们很大的支持,他们长期以来一直热心地帮助别人,解答问题,我们希望对他们表示感谢。“超级用户” 的活动是我们论坛的一个传统,是我们用来表达感谢的方式,感谢他们的参与,积极热心地帮助大家,让这里的新老用户都感受到论坛的热烈气氛。我们非常高兴的告诉大家,我们已经在新的
谷歌中文网站管理员支持论坛里面正式启动了“超级用户” 的活动。

经过谷歌中文网站管理员支持论坛小组的讨论,我们评选出了新一轮的超级用户:“
唏嘘一世”。他在论坛里不仅提出问题,而且与大家分享了很多经验。在过去的几个月里,他一直都非常活跃、积极地帮助其他用户,为大家热心地提出了很多有用的建议,发表了160 多条回复。在向他表示祝贺的同时,我们也期待将来有更多的“超级用户” 的出现!
06:46 Scaling Twitter: Making Twitter 10000 Percent Faster » High Scalability - Building bigger, faster, more reliable websites.

Update 6: Some interesting changes from Twitter's Evan Weaver: everything in RAM now, database is a backup; peaks at 300 tweets/second; every tweet followed by average 126 people; vector cache of tweet IDs; row cache; fragment cache; page cache; keep separate caches; GC makes Ruby optimization resistant so went with Scala; Thrift and HTTP are used internally; 100s internal requests for every external request; rewrote MQ but kept interface the same; 3 queues are used to load balance requests; extensive A/B testing for backwards capability; switched to C memcached client for speed; optimize critical path; faster to get the cached results from the network memory than recompute them locally.
Update 5: Twitter on Scala. A Conversation with Steve Jenson, Alex Payne, and Robey Pointer by Bill Venners. A fascinating discussion of why Twitter moved to the Java JVM for their server infrastructure (long lived processes) and why they moved to Scala to program against it (high level language, static typing, functional). Ruby is used on the front-end but wasn't performant or reliable enough for the back-end.
Update 4: Improving Running Components at Twitter by Evan Weaver. Tells how Twitter changed their infrastructure to go from handling 3 requests to 139 requests a second. They moved to a messaging model, asynchronous process, 3 levels of cache, and moved their middleware to a mixture C and Scala/JVM.
Update 3: Upgrading Twitter without service disruptions by Gojko Adzic. Lots of good updates on the new Twitter architecture.
Update 2: a commenter in Twitter Fails Macworld Keynote Test said this entry needs to be updated. LOL. My uneducated guess is it's not a language or architecture problem, but more a problem of not being able to add hardware fast enough into their data center. The predictability of this problem is debatable, but once you have it, it's hard to fix.
Update: Twitter releases Starling - light-weight persistent queue server that speaks the MemCache protocol. It was built to drive Twitter's backend, and is in production across Twitter's cluster.

read more


^==Back Home: www.chedong.com

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

<== 2009-06-27
  六月 2009  
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          
==> 2009-06-29