high_scalability high_scalability-2012 high_scalability-2012-1323 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Facebook made quite a splash when they released their native iOS app , not because of their app per se, but because of their conclusion that their biggest mistake was betting on HTML5 , so they had to go native. As you might imagine this was a bit like telling a Great White Shark that its bark is worse than its bite. A common refrain was Facebook simply had made a bad HTML5 site, not that HTML5 itself is bad, as plenty of other vendors have made slick well performing mobile sites. An interesting and relevant conversation given the rising butt kickery of mobile. But we were lacking details. Now we aren't. If you were wondering just why Facebook ditched HTML5, Tobie Langel in Perf Feedback - What's slowing down Mobile Facebook , lists out the reasons: Tooling / Developer APIs . Most importantly, the lack of tooling to track down memory problems. Scrolling performance. Scrolling must be fast and smooth and full featured. It's not. GPU. A clunky API and black box ap
sentIndex sentText sentNum sentScore
1 Facebook made quite a splash when they released their native iOS app , not because of their app per se, but because of their conclusion that their biggest mistake was betting on HTML5 , so they had to go native. [sent-1, score-1.072]
2 As you might imagine this was a bit like telling a Great White Shark that its bark is worse than its bite. [sent-2, score-0.211]
3 A common refrain was Facebook simply had made a bad HTML5 site, not that HTML5 itself is bad, as plenty of other vendors have made slick well performing mobile sites. [sent-3, score-0.877]
4 An interesting and relevant conversation given the rising butt kickery of mobile. [sent-4, score-0.551]
5 If you were wondering just why Facebook ditched HTML5, Tobie Langel in Perf Feedback - What's slowing down Mobile Facebook , lists out the reasons: Tooling / Developer APIs . [sent-7, score-0.409]
6 Most importantly, the lack of tooling to track down memory problems. [sent-8, score-0.432]
7 Scrolling must be fast and smooth and full featured. [sent-10, score-0.145]
8 A clunky API and black box approach make it an unreliable accelerator. [sent-13, score-0.235]
9 Would like better touch tracking support, smoother animations, and better caching. [sent-15, score-0.382]
10 Go native, HTML5 is going to lag for a while Facebook explains what's wrong with the mobile web (w3. [sent-17, score-0.406]
wordName wordTfidf (topN-words)
[('tooling', 0.269), ('facebook', 0.21), ('butt', 0.195), ('animations', 0.195), ('ditched', 0.195), ('mobile', 0.192), ('splash', 0.175), ('smoother', 0.175), ('zuckerberg', 0.175), ('articleswhat', 0.168), ('shark', 0.168), ('lacking', 0.159), ('disrupt', 0.159), ('se', 0.151), ('betting', 0.151), ('smooth', 0.145), ('rising', 0.141), ('made', 0.139), ('scrolling', 0.138), ('bad', 0.137), ('slick', 0.131), ('unreliable', 0.127), ('lag', 0.124), ('conversation', 0.118), ('slowing', 0.116), ('mistake', 0.114), ('telling', 0.11), ('black', 0.108), ('importantly', 0.107), ('touch', 0.105), ('conclusion', 0.105), ('ios', 0.105), ('mark', 0.104), ('white', 0.103), ('tracking', 0.102), ('feedback', 0.101), ('worse', 0.101), ('native', 0.1), ('plenty', 0.1), ('app', 0.099), ('wondering', 0.098), ('vendors', 0.098), ('relevant', 0.097), ('lists', 0.093), ('explains', 0.09), ('released', 0.09), ('lack', 0.086), ('performing', 0.08), ('reasons', 0.079), ('track', 0.077)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 1323 high scalability-2012-09-15-4 Reasons Facebook Dumped HTML5 and Went Native
Introduction: Facebook made quite a splash when they released their native iOS app , not because of their app per se, but because of their conclusion that their biggest mistake was betting on HTML5 , so they had to go native. As you might imagine this was a bit like telling a Great White Shark that its bark is worse than its bite. A common refrain was Facebook simply had made a bad HTML5 site, not that HTML5 itself is bad, as plenty of other vendors have made slick well performing mobile sites. An interesting and relevant conversation given the rising butt kickery of mobile. But we were lacking details. Now we aren't. If you were wondering just why Facebook ditched HTML5, Tobie Langel in Perf Feedback - What's slowing down Mobile Facebook , lists out the reasons: Tooling / Developer APIs . Most importantly, the lack of tooling to track down memory problems. Scrolling performance. Scrolling must be fast and smooth and full featured. It's not. GPU. A clunky API and black box ap
2 0.11878074 93 high scalability-2007-09-16-What software runs on this site?
Introduction: It's pretty slick! olla
3 0.11464944 845 high scalability-2010-06-22-Exploring the software behind Facebook, the world’s largest site
Introduction: Peter Alguacil at Pingdom wrote a HighScalability worthy article on Facebook's architecture: Exploring the software behind Facebook, the world’s largest site . It covers the challenges Facebook faces, the software Facebook uses, and the techniques Facebook uses to keep on scaling. Definitely worth a look.
4 0.1108179 720 high scalability-2009-10-12-High Performance at Massive Scale – Lessons learned at Facebook
Introduction: Jeff Rothschild, Vice President of Technology at Facebook gave a great presentation at UC San Diego on our favorite subject: " High Performance at Massive Scale – Lessons learned at Facebook ". The abstract for the talk is: Facebook has grown into one of the largest sites on the Internet today serving over 200 billion pages per month. The nature of social data makes engineering a site for this level of scale a particularly challenging proposition. In this presentation, I will discuss the aspects of social data that present challenges for scalability and will describe the the core architectural components and design principles that Facebook has used to address these challenges. In addition, I will discuss emerging technologies that offer new opportunities for building cost-effective high performance web architectures. There's a lot of interesting about this talk that we'll get into later, but I thought you might want a head start on learning how Facebook handles 30K+ machines,
Introduction: Facebook has been teasing us. While many of their recent acquisitions have been surprising, shocking is the only word adequately describing Facebook's 5 day whirlwind acquisition of Oculus , immersive virtual reality visionaries, for a now paltry sounding $2 billion. The backlash is a pandemic, jumping across social networks with the speed only a meme powered by the directly unaffected can generate. For more than 30 years VR has been the dream burning in the heart of every science fiction fan. Now that this future might finally be here, Facebook’s ownage makes it seem like a wonderful and hopeful timeline has been choked off, killing the Metaverse before it even had a chance to begin. For the many who voted for an open future with their Kickstarter dollars , there’s a deep and personal sense of betrayal, despite Facebook’s promise to leave Oculus alone. The intensity of the reaction is because Oculus matters to people. It's new, it's different, it create
6 0.10012516 1123 high scalability-2011-09-23-The Real News is Not that Facebook Serves Up 1 Trillion Pages a Month…
7 0.097753339 624 high scalability-2009-06-10-Hive - A Petabyte Scale Data Warehouse using Hadoop
8 0.096357167 1333 high scalability-2012-10-04-LinkedIn Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster
9 0.094424188 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month
10 0.08865118 721 high scalability-2009-10-13-Why are Facebook, Digg, and Twitter so hard to scale?
11 0.088618703 464 high scalability-2008-12-13-Strategy: Facebook Tweaks to Handle 6 Time as Many Memcached Requests
12 0.082404867 1085 high scalability-2011-07-25-Is NoSQL a Premature Optimization that's Worse than Death? Or the Lady Gaga of the Database World?
13 0.079690225 1190 high scalability-2012-02-10-Stuff The Internet Says On Scalability For February 10, 2012
14 0.077746771 1011 high scalability-2011-03-25-Did the Microsoft Stack Kill MySpace?
15 0.076740399 1575 high scalability-2014-01-08-Under Snowden's Light Software Architecture Choices Become Murky
16 0.075364962 1008 high scalability-2011-03-22-Facebook's New Realtime Analytics System: HBase to Process 20 Billion Events Per Day
17 0.074602708 1602 high scalability-2014-02-26-The WhatsApp Architecture Facebook Bought For $19 Billion
18 0.070717439 1179 high scalability-2012-01-23-Facebook Timeline: Brought to You by the Power of Denormalization
19 0.069199443 1520 high scalability-2013-09-20-Stuff The Internet Says On Scalability For September 20, 2013
20 0.068651602 1303 high scalability-2012-08-13-Ask HighScalability: Facing scaling issues with news feeds on Redis. Any advice?
topicId topicWeight
[(0, 0.096), (1, 0.049), (2, 0.014), (3, 0.005), (4, 0.036), (5, -0.047), (6, -0.046), (7, 0.069), (8, 0.052), (9, -0.008), (10, -0.004), (11, 0.027), (12, 0.033), (13, 0.036), (14, -0.051), (15, 0.014), (16, 0.04), (17, 0.0), (18, 0.028), (19, 0.009), (20, 0.048), (21, 0.05), (22, 0.046), (23, 0.021), (24, 0.047), (25, -0.038), (26, 0.027), (27, -0.067), (28, 0.018), (29, -0.017), (30, -0.121), (31, -0.017), (32, 0.017), (33, 0.008), (34, 0.019), (35, 0.04), (36, 0.03), (37, -0.02), (38, -0.038), (39, -0.018), (40, -0.046), (41, -0.001), (42, 0.036), (43, -0.005), (44, 0.025), (45, 0.016), (46, -0.011), (47, 0.031), (48, -0.024), (49, -0.014)]
simIndex simValue blogId blogTitle
same-blog 1 0.98545647 1323 high scalability-2012-09-15-4 Reasons Facebook Dumped HTML5 and Went Native
Introduction: Facebook made quite a splash when they released their native iOS app , not because of their app per se, but because of their conclusion that their biggest mistake was betting on HTML5 , so they had to go native. As you might imagine this was a bit like telling a Great White Shark that its bark is worse than its bite. A common refrain was Facebook simply had made a bad HTML5 site, not that HTML5 itself is bad, as plenty of other vendors have made slick well performing mobile sites. An interesting and relevant conversation given the rising butt kickery of mobile. But we were lacking details. Now we aren't. If you were wondering just why Facebook ditched HTML5, Tobie Langel in Perf Feedback - What's slowing down Mobile Facebook , lists out the reasons: Tooling / Developer APIs . Most importantly, the lack of tooling to track down memory problems. Scrolling performance. Scrolling must be fast and smooth and full featured. It's not. GPU. A clunky API and black box ap
Introduction: Facebook has been teasing us. While many of their recent acquisitions have been surprising, shocking is the only word adequately describing Facebook's 5 day whirlwind acquisition of Oculus , immersive virtual reality visionaries, for a now paltry sounding $2 billion. The backlash is a pandemic, jumping across social networks with the speed only a meme powered by the directly unaffected can generate. For more than 30 years VR has been the dream burning in the heart of every science fiction fan. Now that this future might finally be here, Facebook’s ownage makes it seem like a wonderful and hopeful timeline has been choked off, killing the Metaverse before it even had a chance to begin. For the many who voted for an open future with their Kickstarter dollars , there’s a deep and personal sense of betrayal, despite Facebook’s promise to leave Oculus alone. The intensity of the reaction is because Oculus matters to people. It's new, it's different, it create
3 0.8108052 845 high scalability-2010-06-22-Exploring the software behind Facebook, the world’s largest site
Introduction: Peter Alguacil at Pingdom wrote a HighScalability worthy article on Facebook's architecture: Exploring the software behind Facebook, the world’s largest site . It covers the challenges Facebook faces, the software Facebook uses, and the techniques Facebook uses to keep on scaling. Definitely worth a look.
4 0.79065555 264 high scalability-2008-03-03-Read This Site and Ace Your Next Interview!
Introduction: Paul Tyma published a massive and massively good 96 page insider's manual on How to Pass a Silicon Valley Software Engineering Interview . My eyes immediately latched on to one of his key example scenarios, which involves scaling Facebook: Facebook ● What was Facebook day 1? – A database with a PHP front-end ● In PHP, Java, C#, whatever – How long would it take you to reproduce Facebook's first incarnation? ● A single MySQL instance with some simple queries probably used to happily query the whole userbase. Facebook ● What is it today? ● Its not about “that stuff you learned in school” – Its about what a company with thousands of (possibly conflicting) queries per second operating on a directed-graph with 50 million nodes ● And of course a few Petabytes of data ● And 99.99% uptime ● Design decision? A Facebook user is (or recently was) currently limited to 5000 friends. If you've been reading all the wisdom contributed to and reference
5 0.74870318 966 high scalability-2010-12-31-Facebook in 20 Minutes: 2.7M Photos, 10.2M Comments, 4.6M Messages
Introduction: To celebrate the new year Facebook has shared the results of a little end of the year introspection. It has been a fecund year for Facebook: 43,869,800 changed their status to single 3,025,791 changed their status to "it's complicated" 28,460,516 changed their status to in a relationship 5,974,574 changed their status to engaged 36,774,801 changes their status to married If these numbers are simply to large to grasp, it doesn't get any better when you look at happens in a mere 20 minutes: Shared links: 1,000,000 Tagged photos: 1,323,000 Event invites sent out: 1,484,000 Wall Posts: 1,587,000 Status updates: 1,851,000 Friend requests accepted: 1,972,000 Photos uploaded: 2,716,000 Comments: 10,208,000 Message: 4,632,000 If you want to see how Facebook supports these huge numbers take a look at a few posts . One wonders what the new year will bring? Related Articles What the World Eats from Time Magazine A Day in the Life of an An
6 0.73509651 624 high scalability-2009-06-10-Hive - A Petabyte Scale Data Warehouse using Hadoop
7 0.72892499 720 high scalability-2009-10-12-High Performance at Massive Scale – Lessons learned at Facebook
8 0.72383547 1081 high scalability-2011-07-18-Building your own Facebook Realtime Analytics System
9 0.7207197 562 high scalability-2009-04-10-Facebook's Aditya giving presentation on Facebook Architecture
10 0.70502025 599 high scalability-2009-05-14-Who Has the Most Web Servers?
11 0.67059648 870 high scalability-2010-08-02-7 Scaling Strategies Facebook Used to Grow to 500 Million Users
12 0.65233749 378 high scalability-2008-09-03-Some Facebook Secrets to Better Operations
13 0.65099496 792 high scalability-2010-03-10-How FarmVille Scales - The Follow-up
14 0.63940948 840 high scalability-2010-06-10-The Four Meta Secrets of Scaling at Facebook
15 0.6261611 1274 high scalability-2012-06-29-Stuff The Internet Says On Scalability For June 29, 2012 - The Velocity Edition
16 0.62260109 1223 high scalability-2012-04-06-Stuff The Internet Says On Scalability For April 6, 2012
17 0.6216982 1444 high scalability-2013-04-23-Facebook Secrets of Web Performance
19 0.61842275 1561 high scalability-2013-12-09-Site Moves from PHP to Facebook's HipHop, Now Pages Load in .6 Seconds Instead of Five
20 0.61266094 1123 high scalability-2011-09-23-The Real News is Not that Facebook Serves Up 1 Trillion Pages a Month…
topicId topicWeight
[(1, 0.043), (2, 0.196), (10, 0.089), (59, 0.31), (61, 0.126), (79, 0.082), (94, 0.051)]
simIndex simValue blogId blogTitle
same-blog 1 0.87628359 1323 high scalability-2012-09-15-4 Reasons Facebook Dumped HTML5 and Went Native
Introduction: Facebook made quite a splash when they released their native iOS app , not because of their app per se, but because of their conclusion that their biggest mistake was betting on HTML5 , so they had to go native. As you might imagine this was a bit like telling a Great White Shark that its bark is worse than its bite. A common refrain was Facebook simply had made a bad HTML5 site, not that HTML5 itself is bad, as plenty of other vendors have made slick well performing mobile sites. An interesting and relevant conversation given the rising butt kickery of mobile. But we were lacking details. Now we aren't. If you were wondering just why Facebook ditched HTML5, Tobie Langel in Perf Feedback - What's slowing down Mobile Facebook , lists out the reasons: Tooling / Developer APIs . Most importantly, the lack of tooling to track down memory problems. Scrolling performance. Scrolling must be fast and smooth and full featured. It's not. GPU. A clunky API and black box ap
2 0.80462676 1582 high scalability-2014-01-20-8 Ways Stardog Made its Database Insanely Scalable
Introduction: Stardog makes a commercial graph database that is a great example of what can be accomplished with a scale-up strategy on BigIron. In a recent article StarDog described how they made their new 2.1 release insanely scalable, improving query scalability by about 3 orders of magnitude and it can now handle 50 billion triples on a $10,000 server with 32 cores and 256 GB RAM. It can also load 20B datasets at 300,000 triples per second. What did they do that you can also do? Avoid locks by using non-blocking algorithms and data structures . For example, moving from BitSet to ConcurrentLinkedQueue. Use ThreadLocal aggressively to reduce thread contention and avoid synchronization . Batch LRU evictions in a single thread . Triggered by several LRU caches becoming problematic when evictions were being swamped by additions. Downside is batching increases memory pressure and GC times. Move to SHA1 for hashing URIs, bnodes, and literal values . Making hash collisions nearly imp
3 0.8016153 1314 high scalability-2012-08-30-Dramatically Improving Performance by Debugging Brutally Complex Prolems
Introduction: Debugging complex problems is 90% persistence and 50% cool tools. Brendan Gregg in 10 Performance Wins tells a fascinating story of how a team at Joyent solved some weird and challenging performance issues deep in the OS. It took lots of effort, DTrace , Flame Graphs , USE Method , and writing custom tools when necessary. Here's a quick summary of the solved cases: Monitoring. 1000x improvement . An application blocked while paging anonymous memory back in. It was also blocked during file system fsync() calls. The application was misconfigured and sometimes briefly exceeded available memory, getting page out. Riak. 2x improvement . The Erlang VM used half the CPU count it was supposed to, so CPUs remained unused. Fix was a configuration change. MySQL. 380x improvement . Reads were slow. Cause was correlated writes. Fix was to tune the cache flush interval on the storage controller. Various. 2800x improvement . Large systems calls to getvmusage() could take a few sec
4 0.7988047 530 high scalability-2009-03-11-13 Screencasts on How to Scale Rails
Introduction: Gregg Pollack has made 13 screen casts on how to scale rails: Episode #1 - Page Responsiveness Episode #2 - Page Caching Episode #3 - Cache Expiration Episode #4 - New Relic RPM Episode #5 - Advanced Page Caching Episode #6 - Action Caching Episode #7 - Fragment Caching Episode #8 - Memcached Episode #9 - Taylor Weibley & Databases Episode #10 - Client-side Caching Episode #11 - Advanced HTTP Caching Episode #12 - Jesse Newland & Deployment Episode #13 - Jim Gochee & Advanced RPM For a good InfoQ interview with Greg take a look at Gregg Pollack and the How-To of Scaling Rails .
5 0.78532219 1536 high scalability-2013-10-23-Strategy: Use Linux Taskset to Pin Processes or Let the OS Schedule It?
Introduction: This question comes from Ulysses on an interesting thread from the Mechanical Sympathy news group, especially given how multiple processors are now the norm: Ulysses: On an 8xCPU Linux instance, is it at all advantageous to use the Linux taskset command to pin an 8xJVM process set (co-ordinated as a www.infinispan.org distributed cache/data grid) to a specific CPU affinity set (i.e. pin JVM0 process to CPU 0, JVM1 process to CPU1, ...., JVM7process to CPU 7) vs. just letting the Linux OS use its default mechanism for provisioning the 8xJVM process set to the available CPUs? In effrort to seek an optimal point (in the full event space), what are the conceptual trade-offs in considering "searching" each permutation of provisioning an 8xJVM process set to an 8xCPU set via taskset? Given taskset is they key to the question, it would help to have a definition: Used to set or retrieve the CPU affinity of a running process given its PID or to launch a new COMMAND with
6 0.7846278 656 high scalability-2009-07-16-Scalable Web Architectures and Application State
7 0.77841347 1218 high scalability-2012-03-29-Strategy: Exploit Processor Affinity for High and Predictable Performance
8 0.74879962 850 high scalability-2010-06-30-Paper: GraphLab: A New Framework For Parallel Machine Learning
9 0.68930292 609 high scalability-2009-05-28-Scaling PostgreSQL using CUDA
10 0.68797338 1281 high scalability-2012-07-11-FictionPress: Publishing 6 Million Works of Fiction on the Web
11 0.68578494 1634 high scalability-2014-04-18-Stuff The Internet Says On Scalability For April 18th, 2014
12 0.65402615 1264 high scalability-2012-06-15-Cloud Bursting between AWS and Rackspace
13 0.65085006 1038 high scalability-2011-05-11-Troubleshooting response time problems – why you cannot trust your system metrics
14 0.64763856 1246 high scalability-2012-05-16-Big List of 20 Common Bottlenecks
15 0.63419455 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
16 0.63324946 1183 high scalability-2012-01-30-37signals Still Happily Scaling on Moore RAM and SSDs
17 0.63321626 1551 high scalability-2013-11-20-How Twitter Improved JVM Performance by Reducing GC and Faster Memory Allocation
18 0.62541026 1142 high scalability-2011-11-14-Using Gossip Protocols for Failure Detection, Monitoring, Messaging and Other Good Things
19 0.6233505 1337 high scalability-2012-10-10-Antirez: You Need to Think in Terms of Organizing Your Data for Fetching
20 0.62270635 943 high scalability-2010-11-16-Facebook's New Real-time Messaging System: HBase to Store 135+ Billion Messages a Month