本文摘录一篇文章,作者整理了现在大数据使用的一些…
直接附原文和他们的成果图.
翻墙_二三事
1,
今天和一位素未谋面聊过几次的网友聊了几句,得知已经去了新西兰,该国IT行业就业环境不是很好,但还是找了一份编程的工作,除了得享新西兰大自然的赋予之外,工作又轻松愉快,摆脱国内经常无效率加班,廉价技术劳动力的怨念,打算在异国他乡发展。
听完后,很高兴。
Why_we_dont_have_benchmarks_comparing_Redis_with_other_DBs
Antirez于前几日发布了一篇blog,Why we don’t have benchmarks comparing Redis with other DBs
原文戳上面的链接,这里摘录:
Redis speed could be one selling point for new users, so following the trend of comparative “advertising” it should be logical to have a few comparisons at Redis.io. However there are two problems with this. One is of goals: I don’t want to convince developers to adopt Redis, we just do our best in order to provide a suitable product, and we are happy if people can get work done with it, that’s where my marketing wishes end. There is more: it is almost always impossible to compare different systems in a fair way.
When you compare two databases, to get fair numbers, they need to share *a lot*: data model, exact durability guarantees, data replication safety, availability during partitions, and so forth: often a system will score in a lower way than another system since it sacrifices speed to provide less “hey look at me” qualities but that are very important nonetheless. Moreover the testing suite is a complex matter as well unless different database systems talk the same exact protocol: differences in the client library alone can contribute for large differences.
短句2
风起的时候,尘土飞扬。
风落的时候,尘归尘,土归土。
这一次再见,四目对视数秒,
这一刻,意识到,我又能怎样,又能改变什么?
也在这一刻悟到,
有更多更有意义的事。
–2015于携程年会散场
先秦古文一篇《谏逐客书》
臣闻吏议逐客,窃以为过矣。昔穆公求士,西取由余于戎,东得百里奚于宛,迎蹇叔于宋,来邳豹、公孙支于晋。此五子者,不产于秦,而穆公用之,并国二十,遂霸西戎。孝公用商鞅之法,移风易俗,民以殷盛,国以富强,百姓乐用,诸侯亲服,获楚、魏之师,举地千里,至今治强。惠王用张仪之计,拔三川之地,西并巴、蜀,北收上郡,南取汉中,包九夷,制鄢、郢,东据成皋之险,割膏腴之壤,遂散六国之众,使之西面事秦,功施到今。昭王得范雎,废穰侯,逐华阳,强公室,杜私门,蚕食诸侯,使秦成帝业。此四君者,皆以客之功。由此观之,客何负于秦哉!向使四君却客而不内,疏士而不用,是使国无富利之实,而秦无强大之名也。
记录一篇文章_scaling-postgresql-at-braintree-four-years-of-evolution
braintree的MySQL迁移Postgresql遇到的问题及解决方案
https://www.braintreepayments.com/braintrust/scaling-postgresql-at-braintree-four-years-of-evolution
一个酷酷的网页
https://www.braintreepayments.com/about
link2
https://speakerdeck.com/pgr0ss/high-availability-at-braintree
新浪微博明文发送信息,搜狗输入法收集设备信息
先看solidot一则新闻:原文链接
迈克菲实验室称,新浪微博App通过明文HTTP发送消息,用户没有任何隐私,
攻击者很容易收集Cookie,或通过中间人攻击修改信息,比如插入恶意链接。
利用 Wireshark捕捉流量,用户通过聊天窗口与朋友的聊天记录完全一览无余。
迈克菲实验室还发现,搜狗输入法会收集用户插入到电脑上的设备的信息,
然后明文HTTP发送出去。
爱而知其恶,恶而知其美
身为中国自由主义旗手的胡适,想必就不会首肯这本书。胡适曾经被鲁迅骂为“高等华人”、“金元博士”、“日本帝国主义的军师”,但当苏雪林向其控诉鲁迅的种种恶行时,胡适却坚持认为,凡论一人,要“爱而知其恶,恶而知其美”,虽然“鲁迅狺狺攻击我们”,但“鲁迅自有他的长处,他的早年文学作品,如他的小说史研究,皆是上等工作。”
how-twitter-uses-redis-to-scale-105tb-ram-39mm-qps-10000-ins
原文见:how-twitter-uses-redis-to-scale-105tb-ram-39mm-qps-10000-ins
原文讲述作者在twitter使用redis进行scale-105tb-ram-39mm-qps-10000-ins的一些经验(其实主要列举了搭建large-scale系统需要考虑的一些情况,这点还是很值得看一下的;也讨论了这种环境下使用redis需要考虑的因素)
- Why Redis?
- Hybrid List
- BTree
- Cluster Management
- Data Insight
- Wish List for Redis
几个好的总结:
(嗯,第六点?)
Scale demands predictability.
The larger the cluster, the more customers, the more predictable and deterministic you want your service to be. When there’s one customer and there’s a problem you can dig into a problem and it’s intriguing. When you have 70 customers you can’t keep up.
antirez的抱怨
针对他人twitter上的争论,其实antirez正文写的是很平淡客观的,今天偶然翻看评论,antirez对一位留言者做了回复,这里不难明白作者标题的含义了
Dermot Haughey留言:
|
|