high_scalability high_scalability-2014 high_scalability-2014-1587 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Monitor, monitor, monitor. That's the advice every startup gives once they reach a certain size. But can you ever monitor enough? If you are Bitly and everyone will complain when you are down, probably not. Here are 10 Things We Forgot to Monitor from Bitly, along with good stories and copious amounts of code snippets. Well worth reading, especially after you've already started monitoring the lower hanging fruit. An interesting revelation from the article is that: We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2. Fork Rate . A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. Flow control packets . A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic. Swap In/Out Rate . Measure the right thing. It's the rate memory is swapped
sentIndex sentText sentNum sentScore
1 That's the advice every startup gives once they reach a certain size. [sent-2, score-0.14]
2 If you are Bitly and everyone will complain when you are down, probably not. [sent-4, score-0.205]
3 Here are 10 Things We Forgot to Monitor from Bitly, along with good stories and copious amounts of code snippets. [sent-5, score-0.085]
4 Well worth reading, especially after you've already started monitoring the lower hanging fruit. [sent-6, score-0.112]
5 An interesting revelation from the article is that: We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2. [sent-7, score-0.62]
6 A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. [sent-9, score-0.402]
7 A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic. [sent-11, score-0.655]
8 It's the rate memory is swapped in/out that can impact performance, not the quantity. [sent-14, score-0.235]
9 Use an init script to capture when servers are dying. [sent-16, score-0.406]
10 If you are not checking one of you servers is probably not properly time synced. [sent-19, score-0.347]
11 This is a key part of your infrastructure that often goes unchecked. [sent-21, score-0.074]
12 Also verify External DNS servers give the correct answers and are available. [sent-24, score-0.338]
13 Monitor the outputs from OMSA to know when failures have occurred. [sent-29, score-0.117]
14 Do you know how close you are to your connection limits? [sent-31, score-0.122]
15 It's important to have visibility into your load balancer status by making the health stats visible. [sent-33, score-0.223]
wordName wordTfidf (topN-words)
[('bitly', 0.424), ('omsa', 0.331), ('monitor', 0.246), ('dns', 0.163), ('init', 0.15), ('balancer', 0.143), ('ntp', 0.135), ('swapped', 0.135), ('certificates', 0.13), ('revelation', 0.126), ('forgot', 0.122), ('connection', 0.122), ('quantity', 0.119), ('disable', 0.117), ('outputs', 0.117), ('fork', 0.117), ('flow', 0.116), ('temporarily', 0.114), ('complain', 0.114), ('hanging', 0.112), ('dying', 0.11), ('expiration', 0.102), ('verify', 0.101), ('rate', 0.1), ('boot', 0.096), ('visible', 0.093), ('probably', 0.091), ('administrator', 0.089), ('checking', 0.088), ('clock', 0.088), ('dell', 0.088), ('script', 0.086), ('servers', 0.086), ('stories', 0.085), ('capture', 0.084), ('configuration', 0.082), ('properly', 0.082), ('die', 0.081), ('strange', 0.08), ('health', 0.08), ('answers', 0.078), ('packets', 0.077), ('dropped', 0.077), ('often', 0.074), ('correct', 0.073), ('control', 0.072), ('advice', 0.07), ('second', 0.07), ('reach', 0.07), ('hundred', 0.07)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 1587 high scalability-2014-01-29-10 Things Bitly Should Have Monitored
Introduction: Monitor, monitor, monitor. That's the advice every startup gives once they reach a certain size. But can you ever monitor enough? If you are Bitly and everyone will complain when you are down, probably not. Here are 10 Things We Forgot to Monitor from Bitly, along with good stories and copious amounts of code snippets. Well worth reading, especially after you've already started monitoring the lower hanging fruit. An interesting revelation from the article is that: We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2. Fork Rate . A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. Flow control packets . A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic. Swap In/Out Rate . Measure the right thing. It's the rate memory is swapped
2 0.13123828 1517 high scalability-2013-09-16-The Hidden DNS Tax - Cascading Timeouts and Errors
Introduction: This is a guest post by Nick Burling , VP of Product Management of Bluestripe . Readers of High Scalability know are well versed in performance optimization techniques. Reverse proxies, Varnish, Redis — you hear about them daily. But what you may not realize is that one of the oldest technologies in your stack can be one of your biggest bottlenecks: DNS. People don't spend a lot of time thinking about DNS. It's not sexy. It's an infrastructure service, and it's just supposed to work. At BlueStripe, we work with many teams running applications that support millions of web requests a day. We keep seeing DNS delays and errors that the platform operations team never knows about. It's so common we've start calling it the Hidden DNS Tax . What is the Hidden DNS Tax? The Hidden DNS Tax is a hard-to-see performance hit your users take from DNS timeouts and errors in your back-end architecture. We've seen it bring down the main web application for a Fortune 10 company.
3 0.11115596 987 high scalability-2011-02-10-Dispelling the New SSL Myth
Introduction: Warning, this post is a bit vendor FUDy, but SSL is an important topic and it does bring up some issues worth arguing about. Hacker News has a good discussion of the article. Adam Langley started it all with his article Overclocking SSL and has made a rebuttal to the F5 article in Still not computationally expensive . My car is eight years old this year. It has less than 30,000 miles on it. Yes, you heard that right, less than 30,000 miles. I don’t drive my car very often because, well, my commute is a short trip down two flights of stairs. I don’t need to go very far when I do drive it’s only ten miles or so round trip to the grocery store. So from my perspective, gas isn’t really very expensive. I may use a tank of gas a month, which works out to … well, it’s really not even worth mentioning the cost. But for someone who commutes every day – especially someone who commutes a long-distance every day – gas is expensive. It’s a significant expense every month for them and th
4 0.097945966 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
Introduction: Update 8 : The Cost of Latency by James Hamilton. James summarizing some latency info from Steve Souder , Greg Linden , and Marissa Mayer . Speed [is] an undervalued and under-discussed asset on the web. Update 7: How do you know when you need more memcache servers? . Dathan Pattishall talks about using memcache not to scale, but to reduce latency and reduce I/O spikes, and how to use stats to know when more servers are needed. Update 6: Stock Traders Find Speed Pays, in Milliseconds . Goldman Sachs is making record profits off a 500 millisecond trading advantage. Yes, latency matters. As an interesting aside, Libet found 500 msecs is about the time it takes the brain to weave together an experience of consciousness from all our sensor inputs. Update 5: Shopzilla's Site Redo - You Get What You Measure . At the Velocity conference Phil Dixon, from Shopzilla, presented data showing a 5 second speed up resulted in a 25% increase in page views, a 10% increas
Introduction: Who's Hiring? Torbit is hiring ! Care about performance? Care about making the internet faster and better? At Torbit we use lots of Golang, Node.js, JavaScript and PHP to solve big challenges. Fun and Informative Events GigaSpaces Upcoming Events: webinar on Transactional Cross-Site Data Replication , CloudCamp lightning talk , A Groovy Kind of Java , Cloud Computing World Forum , QCon . Cool Products and Services New Relic - real user monitoring optimize for humans, not bots. Live application stats, SQL/NoSQL performance, web transactions, proactive notifications. Take 2 minutes to sign up for a free trial. NetDNA , a Tier-1 GlobalContent Delivery Network, offers a Dual-CDN strategy which allows companies to utilize a redundant infrastructure while leveraging the advantages of multiple CDNs to reduce costs. Digital Ocean is a Simple Cloud Hosting platform that offers Free Unlimited Bandwidth and Virtual Servers from $10 per month. Sign up f
6 0.096238464 1423 high scalability-2013-03-13-Iron.io Moved From Ruby to Go: 28 Servers Cut and Colossal Clusterf**ks Prevented
8 0.091154262 1038 high scalability-2011-05-11-Troubleshooting response time problems – why you cannot trust your system metrics
12 0.085601389 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
13 0.085123785 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure
15 0.084015295 773 high scalability-2010-02-06-GEO-aware traffic load balancing and caching at CNBC.com
20 0.080243669 905 high scalability-2010-09-21-Sponsored Post: Joyent, DeviantART, CloudSigma, ManageEngine, Site24x7
topicId topicWeight
[(0, 0.148), (1, 0.014), (2, -0.01), (3, -0.057), (4, -0.032), (5, -0.033), (6, 0.07), (7, 0.023), (8, -0.017), (9, -0.04), (10, -0.018), (11, 0.002), (12, 0.014), (13, -0.025), (14, -0.014), (15, 0.017), (16, 0.061), (17, 0.024), (18, -0.03), (19, 0.029), (20, 0.037), (21, 0.012), (22, -0.012), (23, -0.035), (24, 0.008), (25, 0.046), (26, -0.023), (27, 0.049), (28, -0.049), (29, 0.026), (30, -0.027), (31, 0.005), (32, 0.01), (33, 0.021), (34, 0.022), (35, 0.015), (36, 0.031), (37, 0.02), (38, -0.044), (39, 0.04), (40, -0.023), (41, 0.016), (42, 0.017), (43, 0.007), (44, 0.047), (45, 0.076), (46, 0.04), (47, 0.007), (48, 0.031), (49, -0.021)]
simIndex simValue blogId blogTitle
same-blog 1 0.96454459 1587 high scalability-2014-01-29-10 Things Bitly Should Have Monitored
Introduction: Monitor, monitor, monitor. That's the advice every startup gives once they reach a certain size. But can you ever monitor enough? If you are Bitly and everyone will complain when you are down, probably not. Here are 10 Things We Forgot to Monitor from Bitly, along with good stories and copious amounts of code snippets. Well worth reading, especially after you've already started monitoring the lower hanging fruit. An interesting revelation from the article is that: We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2. Fork Rate . A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. Flow control packets . A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic. Swap In/Out Rate . Measure the right thing. It's the rate memory is swapped
2 0.74740809 878 high scalability-2010-08-12-Strategy: Terminate SSL Connections in Hardware and Reduce Server Count by 40%
Introduction: This is an interesting tidbit from near the end of the Packet Pushers podcast Show 15 – Saving the Web With Dinky Putt Putt Firewalls . The conversation was about how SSL connections need to terminate before they can be processed by a WAF ( Web Application Firewall ), which inspects HTTP for security problems like SQL injection and cross-site scripting exploits. Much was made that if programmers did their job better these appliances wouldn't be necessary, but I digress. To terminate SSL most shops run SSL connections into Intel based Linux boxes running Apache. This setup is convenient for developers, but it's not optimized for SSL, so it's slow and costly. Much of the capacity of these servers are unnecessarily consumed processing SSL. Load balancers on the other hand have crypto cards that terminate SSL very efficiently in hardware. Efficiently enough that if you are willing to get rid of the general purpose Linux boxes and use your big iron load balancers, your server count c
3 0.71793473 217 high scalability-2008-01-17-Load Balancing of web server traffic
Introduction: How to detect Congestion occurence in the network? Parameter of Load Balancer?
4 0.71681958 1517 high scalability-2013-09-16-The Hidden DNS Tax - Cascading Timeouts and Errors
Introduction: This is a guest post by Nick Burling , VP of Product Management of Bluestripe . Readers of High Scalability know are well versed in performance optimization techniques. Reverse proxies, Varnish, Redis — you hear about them daily. But what you may not realize is that one of the oldest technologies in your stack can be one of your biggest bottlenecks: DNS. People don't spend a lot of time thinking about DNS. It's not sexy. It's an infrastructure service, and it's just supposed to work. At BlueStripe, we work with many teams running applications that support millions of web requests a day. We keep seeing DNS delays and errors that the platform operations team never knows about. It's so common we've start calling it the Hidden DNS Tax . What is the Hidden DNS Tax? The Hidden DNS Tax is a hard-to-see performance hit your users take from DNS timeouts and errors in your back-end architecture. We've seen it bring down the main web application for a Fortune 10 company.
5 0.71194142 1329 high scalability-2012-09-26-WordPress.com Serves 70,000 req-sec and over 15 Gbit-sec of Traffic using NGINX
Introduction: This is a guest post by Barry Abrahamson , Chief Systems Wrangler at Automattic, and Nginx's Coufounder Andrew Alexeev. WordPress.com serves more than 33 million sites attracting over 339 million people and 3.4 billion pages each month. Since April 2008, WordPress.com has experienced about 4.4 times growth in page views. WordPress.com VIP hosts many popular sites including CNN’s Political Ticker, NFL, Time Inc’s The Page, People Magazine’s Style Watch, corporate blogs for Flickr and KROQ, and many more. Automattic operates two thousand servers in twelve, globally distributed, data centers. WordPress.com customer data is instantly replicated between different locations to provide an extremely reliable and fast web experience for hundreds of millions of visitors. Problem WordPress.com, which began in 2005, started on shared hosting, much like all of the WordPress.org sites. It was soon moved to a single dedicated server and then to two servers. In late 2005, WordPress.com
6 0.69074011 773 high scalability-2010-02-06-GEO-aware traffic load balancing and caching at CNBC.com
7 0.6852681 987 high scalability-2011-02-10-Dispelling the New SSL Myth
8 0.68094456 249 high scalability-2008-02-16-S3 Failed Because of Authentication Overload
9 0.67483336 117 high scalability-2007-10-08-Paper: Understanding and Building High Availability-Load Balanced Clusters
10 0.67237628 1209 high scalability-2012-03-14-The Azure Outage: Time Is a SPOF, Leap Day Doubly So
11 0.67052573 138 high scalability-2007-10-30-Feedblendr Architecture - Using EC2 to Scale
12 0.66029871 1335 high scalability-2012-10-08-How UltraDNS Handles Hundreds of Thousands of Zones and Tens of Millions of Records
14 0.64443088 1155 high scalability-2011-12-12-Netflix: Developing, Deploying, and Supporting Software According to the Way of the Cloud
15 0.63878089 788 high scalability-2010-03-04-How MySpace Tested Their Live Site with 1 Million Concurrent Users
16 0.6368444 1423 high scalability-2013-03-13-Iron.io Moved From Ruby to Go: 28 Servers Cut and Colossal Clusterf**ks Prevented
17 0.63228053 228 high scalability-2008-01-28-Product: ISPMan Centralized ISP Management System
18 0.63159603 1438 high scalability-2013-04-10-Check Yourself Before You Wreck Yourself - Avocado's 5 Early Stages of Architecture Evolution
19 0.62335998 771 high scalability-2010-02-04-Hot Scalability Links for February 4, 2010
20 0.61863464 1077 high scalability-2011-07-11-ATMCash Exploits Virtualization for Security - Immutability and Reversion
topicId topicWeight
[(1, 0.114), (2, 0.21), (10, 0.077), (30, 0.035), (47, 0.015), (73, 0.297), (79, 0.088), (94, 0.072)]
simIndex simValue blogId blogTitle
1 0.8797698 217 high scalability-2008-01-17-Load Balancing of web server traffic
Introduction: How to detect Congestion occurence in the network? Parameter of Load Balancer?
2 0.86220258 125 high scalability-2007-10-18-another approach to replication
Introduction: File replication based on erasure codes can reduce total replicas size 2 times and more.
same-blog 3 0.85972965 1587 high scalability-2014-01-29-10 Things Bitly Should Have Monitored
Introduction: Monitor, monitor, monitor. That's the advice every startup gives once they reach a certain size. But can you ever monitor enough? If you are Bitly and everyone will complain when you are down, probably not. Here are 10 Things We Forgot to Monitor from Bitly, along with good stories and copious amounts of code snippets. Well worth reading, especially after you've already started monitoring the lower hanging fruit. An interesting revelation from the article is that: We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2. Fork Rate . A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. Flow control packets . A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic. Swap In/Out Rate . Measure the right thing. It's the rate memory is swapped
Introduction: It's time to do something a little different and for me that doesn't mean cutting off my hair and joining a monastery, nor does it mean buying a cherry red convertible (yet), it means doing a webinar! On December 14th, 2:00 PM - 3:00 PM EST, I'll be hosting What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web Applications . The webinar is sponsored by VoltDB, but it will be completely vendor independent, as that's the only honor preserving and technically accurate way of doing these things. The webinar will run about 60 minutes, with 40 minutes of speechifying and 20 minutes for questions. The hashtag for the event on Twitter will be SQLNoSQL . I'll be monitoring that hashtag if you have any suggestions for the webinar or if you would like to ask questions during the webinar. The motivation for me to do the webinar was a talk I had with another audience member at the NoSQL Evening in Palo Alto . He said he came from a Java background and was confused ab
Introduction: It's time to do something a little different and for me that doesn't mean cutting off my hair and joining a monastery, nor does it mean buying a cherry red convertible (yet), it means doing a webinar! On December 14th, 2:00 PM - 3:00 PM EST, I'll be hosting What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web Applications . The webinar is sponsored by VoltDB, but it will be completely vendor independent, as that's the only honor preserving and technically accurate way of doing these things. The webinar will run about 60 minutes, with 40 minutes of speechifying and 20 minutes for questions. The hashtag for the event on Twitter will be SQLNoSQL . I'll be monitoring that hashtag if you have any suggestions for the webinar or if you would like to ask questions during the webinar. The motivation for me to do the webinar was a talk I had with another audience member at the NoSQL Evening in Palo Alto . He said he came from a Java background and was confused ab
6 0.83532375 471 high scalability-2008-12-19-Gigaspaces curbs latency outliers with Java Real Time
7 0.81454009 1196 high scalability-2012-02-20-Berkeley DB Architecture - NoSQL Before NoSQL was Cool
8 0.80084771 333 high scalability-2008-05-28-Webinar: Designing and Implementing Scalable Applications with Memcached and MySQL
9 0.79781806 1175 high scalability-2012-01-17-Paper: Feeding Frenzy: Selectively Materializing Users’ Event Feeds
10 0.75409806 980 high scalability-2011-01-28-Stuff The Internet Says On Scalability For January 28, 2011
11 0.75233376 33 high scalability-2007-07-26-ThemBid Architecture
12 0.75221157 284 high scalability-2008-03-19-RAD Lab is Creating a Datacenter Operating System
13 0.74497473 192 high scalability-2007-12-25-IBMer Says LAMP Can't Scale
14 0.72987008 795 high scalability-2010-03-16-1 Billion Reasons Why Adobe Chose HBase
15 0.71148276 1642 high scalability-2014-05-02-Stuff The Internet Says On Scalability For May 2nd, 2014
16 0.69896495 1313 high scalability-2012-08-28-Making Hadoop Run Faster
17 0.69558978 986 high scalability-2011-02-10-Database Isolation Levels And Their Effects on Performance and Scalability
18 0.68101364 709 high scalability-2009-09-19-Space Based Programming in .NET
20 0.66402757 5 high scalability-2007-07-10-mixi.jp Architecture