high_scalability high_scalability-2007 high_scalability-2007-72 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Wikimedia is the platform on which Wikipedia, Wiktionary, and the other seven wiki dwarfs are built on. This document is just excellent for the student trying to scale the heights of giant websites. It is full of details and innovative ideas that have been proven on some of the most used websites on the internet. Site: http://wikimedia.org/ Information Sources Wikimedia architecture http://meta.wikimedia.org/wiki/Wikimedia_servers scale-out vs scale-up in the from Oracle to MySQL blog. Platform Apache Linux MySQL PHP Squid LVS Lucene for Search Memcached for Distributed Object Cache Lighttpd Image Server The Stats 8 million articles spread over hundreds of language projects (english, dutch, ...) 10th busiest site in the world (source: Alexa) Exponential growth: doubling every 4-6 months in terms of visitors / traffic / servers 30 000 HTTP requests/s during peak-time 3 Gbit/s of data traffic 3 data centers: Tampa, A
sentIndex sentText sentNum sentScore
1 Wikimedia is the platform on which Wikipedia, Wiktionary, and the other seven wiki dwarfs are built on. [sent-1, score-0.224]
2 This document is just excellent for the student trying to scale the heights of giant websites. [sent-2, score-0.14]
3 5 - 16 GB of memory managed by ~ 6 people 3 clusters on 3 different continents The Architecture Geographic Load Balancing, based on source IP of client resolver, directs clients to the nearest server cluster. [sent-12, score-0.194]
4 Statically mapping IP addresses to countries to clusters HTTP reverse proxy caching implemented using Squid, grouped by text for wiki content and media for images and large static files. [sent-13, score-0.581]
5 55 Squid servers currently, plus 20 waiting for setup. [sent-14, score-0.08]
6 In their primary and regional data center they build text and media clusters built on LVS, CARP Squid, Cache Squid. [sent-17, score-0.424]
7 In the primary datacenter they have the media storage. [sent-18, score-0.126]
8 To make sure the latest revision of all pages are served invalidation requests are sent to all Squid caches. [sent-19, score-0.253]
9 MediaWiki scales well with multiple CPUs, so we buy dual quad-core servers now (8 CPU cores per box) Hardware shared with External Storage and Memcached tasks Memcached is used to cache image metadata, parser data, differences, users and sessions, and revision text. [sent-21, score-0.631]
10 Metadata, such as article revision history, article relations (links, categories etc. [sent-22, score-0.253]
11 ), user accounts and settings are stored in the core databases Actual revision text is stored as blobs in External storage Static (uploaded) files, such as images, are stored separately on the image server - metadata (size, type, etc. [sent-23, score-1.186]
12 ) is cached in the core database and object caches Separate database per wiki (not separate server! [sent-24, score-0.386]
13 Avoid expensive algorithms, database queries, etc. [sent-31, score-0.102]
14 Cache every result that is expensive and has temporal locality of reference. [sent-32, score-0.311]
15 Wikipedia's database servers these days are 16GB dual or quad core boxes with 6 15,000 RPM SCSI drives in a RAID 0 setup. [sent-39, score-0.418]
16 That happens to be the sweet spot for the working set and load balancing setup they have. [sent-40, score-0.171]
17 They would use smaller/cheaper systems if it made sense, but 16GB is right for the working set size and that drives the rest of the spec to match the demands of a system with that much RAM. [sent-41, score-0.141]
18 Similarly the web servers are currently 8 core boxes because that happens to work well for load balancing and gives good PHP throughput with relatively easy load balancing. [sent-42, score-0.603]
19 Wikipedia's MediaWiki was originally written for a single master database server. [sent-44, score-0.087]
20 It's a LOT easier than doing it while load is doubling every few months! [sent-50, score-0.192]
wordName wordTfidf (topN-words)
[('squid', 0.259), ('revision', 0.253), ('text', 0.178), ('serverup', 0.176), ('slaves', 0.169), ('wiki', 0.157), ('wikipedia', 0.152), ('gb', 0.139), ('media', 0.126), ('operations', 0.125), ('metadata', 0.122), ('per', 0.122), ('clusters', 0.12), ('temporal', 0.112), ('core', 0.107), ('expensive', 0.102), ('external', 0.102), ('doubling', 0.101), ('locality', 0.097), ('image', 0.095), ('stored', 0.093), ('load', 0.091), ('master', 0.087), ('date', 0.086), ('dual', 0.081), ('servers', 0.08), ('inexpensively', 0.08), ('masterthe', 0.08), ('nontechnical', 0.08), ('refining', 0.08), ('revisions', 0.08), ('seeming', 0.08), ('virtualisation', 0.08), ('wikimedia', 0.08), ('balancing', 0.08), ('boxes', 0.079), ('accounts', 0.078), ('currently', 0.075), ('dutch', 0.075), ('recalculating', 0.075), ('resolver', 0.075), ('thedata', 0.075), ('server', 0.074), ('heights', 0.071), ('drives', 0.071), ('size', 0.07), ('mediawiki', 0.069), ('student', 0.069), ('ip', 0.068), ('dwarfs', 0.067)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000004 72 high scalability-2007-08-22-Wikimedia architecture
Introduction: Wikimedia is the platform on which Wikipedia, Wiktionary, and the other seven wiki dwarfs are built on. This document is just excellent for the student trying to scale the heights of giant websites. It is full of details and innovative ideas that have been proven on some of the most used websites on the internet. Site: http://wikimedia.org/ Information Sources Wikimedia architecture http://meta.wikimedia.org/wiki/Wikimedia_servers scale-out vs scale-up in the from Oracle to MySQL blog. Platform Apache Linux MySQL PHP Squid LVS Lucene for Search Memcached for Distributed Object Cache Lighttpd Image Server The Stats 8 million articles spread over hundreds of language projects (english, dutch, ...) 10th busiest site in the world (source: Alexa) Exponential growth: doubling every 4-6 months in terms of visitors / traffic / servers 30 000 HTTP requests/s during peak-time 3 Gbit/s of data traffic 3 data centers: Tampa, A
2 0.18776239 195 high scalability-2007-12-28-Amazon's EC2: Pay as You Grow Could Cut Your Costs in Half
Introduction: Update 2: Summize Computes Computing Resources for a Startup . Lots of nice graphs showing Amazon is hard to beat for small machines and become less cost efficient for well used larger machines. Long term storage costs may eat your saving away. And out of cloud bandwidth costs are high. Update: via ProductionScale , a nice Digital Web article on how to setup S3 to store media files and how Blue Origin was able to handle 3.5 million requests and 758 GBs in bandwidth in a single day for very little $$$. Also a Right Scale article on Network performance within Amazon EC2 and to Amazon S3 . 75MB/s between EC2 instances, 10.2MB/s between EC2 and S3 for download, 6.9MB/s upload. Now that Amazon's S3 (storage service) is out of beta and EC2 (elastic compute cloud) has added new instance types (the class of machine you can rent) with more CPU and more RAM, I thought it would be interesting to take a look out how their pricing stacks up. The quick conclusion: the m
3 0.18157046 5 high scalability-2007-07-10-mixi.jp Architecture
Introduction: Mixi is a fast growing social networking site in Japan. They provide services like: diary, community, message, review, and photo album. Having a lot in common with LiveJournal they also developed many of the same approaches. Their write up on how they scaled their system is easily one of the best out there. Site: http://mixi.jp Information Sources mixi.jp - scaling out with open source Platform Linux Apache MySQL Perl Memcached Squid Shard What's Inside? They grew to approximately 4 million users in two years and add over 15,000 new users/day. Ranks 35th on Alexa and 3rd in Japan. More than 100 MySQL servers Add more than 10 servers/month Use non-persistent connections. Diary traffic is 85% read and 15% write. Message traffic is is 75% read and 25% write. Ran into replication performance problems so they had to split the database. Considered splitting vertically by user or splitting horizontally by table type. The ende
4 0.1801735 74 high scalability-2007-08-23-Product: Varnish
Introduction: Varnish is a state-of-the-art, high-performance HTTP accelerator. Varnish is targeted primarily at the FreeBSD 6 and Linux 2.6 platforms, and will take full advantage of the virtual memory system and advanced I/O features offered by these operating systems. Varnish was written from the ground up to be a high performance caching reverse proxy. Squid is a forward proxy that can be configured as a reverse proxy. Besides - Squid is rather old and designed like computer programs where supposed to be designed in 1980. Varnish is reported to be 10x-20x faster than Squid on the same hardware.
5 0.17936906 662 high scalability-2009-07-27-Handle 700 Percent More Requests Using Squid and APC Cache
Introduction: This post on www.ilovebonnie.net documents some impressive system performance improvements by the addition of Squid Cache (a caching proxy) and APC Cache (opcode cache for PHP). Apache is able to deliver roughly 700% more requests per second with Squid when serving 1KB and 100KB images. Server load is reduced using Squid because the server does not have to create a bunch of Apache processes to handle the requests. APC Cache took a system that could barely handle 10-20 requests per second to handling 50-60 requests per second. A 400% increase. APC allowed the load times to remain under 5 seconds even with 200 concurrent threads slamming on the server. These two caches are easy to setup and install and allow you to get a lot more performance out of them. The post has an in-depth discussion and a number of supporting charts. The primary point is how simple it can be to improve performance and scalability by adding caching.
6 0.16519539 248 high scalability-2008-02-13-What's your scalability plan?
7 0.16315025 152 high scalability-2007-11-13-Flickr Architecture
8 0.15969449 134 high scalability-2007-10-26-Paper: Wikipedia's Site Internals, Configuration, Code Examples and Management Issues
10 0.15158816 274 high scalability-2008-03-12-YouTube Architecture
11 0.14482974 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
13 0.14176668 672 high scalability-2009-08-06-An Unorthodox Approach to Database Design : The Coming of the Shard
14 0.1371052 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
15 0.13558042 1440 high scalability-2013-04-15-Scaling Pinterest - From 0 to 10s of Billions of Page Views a Month in Two Years
16 0.13468483 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month
17 0.13415518 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
18 0.13241675 150 high scalability-2007-11-12-Slashdot Architecture - How the Old Man of the Internet Learned to Scale
19 0.13138908 142 high scalability-2007-11-05-Strategy: Diagonal Scaling - Don't Forget to Scale Out AND Up
20 0.13051675 796 high scalability-2010-03-16-Justin.tv's Live Video Broadcasting Architecture
topicId topicWeight
[(0, 0.239), (1, 0.128), (2, -0.056), (3, -0.179), (4, -0.023), (5, 0.021), (6, 0.04), (7, -0.093), (8, -0.033), (9, 0.056), (10, -0.003), (11, -0.093), (12, 0.008), (13, 0.033), (14, 0.002), (15, 0.066), (16, -0.051), (17, 0.033), (18, -0.039), (19, 0.051), (20, -0.024), (21, 0.062), (22, -0.038), (23, -0.067), (24, 0.017), (25, -0.024), (26, 0.036), (27, -0.009), (28, -0.03), (29, 0.032), (30, 0.011), (31, -0.001), (32, -0.077), (33, -0.011), (34, -0.012), (35, -0.022), (36, 0.031), (37, 0.052), (38, 0.021), (39, 0.009), (40, -0.032), (41, 0.007), (42, 0.019), (43, -0.012), (44, 0.026), (45, 0.093), (46, -0.002), (47, -0.022), (48, 0.015), (49, -0.021)]
simIndex simValue blogId blogTitle
same-blog 1 0.96977794 72 high scalability-2007-08-22-Wikimedia architecture
Introduction: Wikimedia is the platform on which Wikipedia, Wiktionary, and the other seven wiki dwarfs are built on. This document is just excellent for the student trying to scale the heights of giant websites. It is full of details and innovative ideas that have been proven on some of the most used websites on the internet. Site: http://wikimedia.org/ Information Sources Wikimedia architecture http://meta.wikimedia.org/wiki/Wikimedia_servers scale-out vs scale-up in the from Oracle to MySQL blog. Platform Apache Linux MySQL PHP Squid LVS Lucene for Search Memcached for Distributed Object Cache Lighttpd Image Server The Stats 8 million articles spread over hundreds of language projects (english, dutch, ...) 10th busiest site in the world (source: Alexa) Exponential growth: doubling every 4-6 months in terms of visitors / traffic / servers 30 000 HTTP requests/s during peak-time 3 Gbit/s of data traffic 3 data centers: Tampa, A
2 0.81969523 150 high scalability-2007-11-12-Slashdot Architecture - How the Old Man of the Internet Learned to Scale
Introduction: Slashdot effect : overwhelming unprepared sites with an avalanche of reader's clicks after being mentioned on Slashdot. Sure, we now have the "Digg effect" and other hot new stars, but Slashdot was the original. And like many stars from generations past, Slashdot plays the elder statesman's role with with class, dignity, and restraint. Yet with millions and millions of users Slashdot is still box office gold and more than keeps up with the young'ins. And with age comes the wisdom of learning how to handle all those users. Just how does Slashdot scale and what can you learn by going old school? Site: http://slashdot.org Information Sources Slashdot's Setup, Part 1- Hardware Slashdot's Setup, Part 2- Software History of Slashdot Part 3- Going Corporate The History of Slashdot Part 4 - Yesterday, Today, Tomorrow The Platform MySQL Linux (CentOS/RHEL) Pound Apache Perl Memcached LVS The Stats Started building the system in 1999
3 0.81235939 391 high scalability-2008-09-23-The 7 Stages of Scaling Web Apps
Introduction: By John Engales CTO, Rackspace. Good presentation of the stages a typical successful website goes through: Stage 1 - The Beginning: Simple architecture, low complexity. no redundancy. Firewall, load balancer, a pair of web servers, database server, and internal storage. Stage 2 - More of the same, just bigger. Stage 3 - The Pain Begins: publicity hits. Use reverse proxy, cache static content, load balancers, more databases, re-coding. Stage 4 - The Pain Intensifies: caching with memcached, writes overload and replication takes too long, start database partitioning, shared storage makes sense for content, significant re-architecting for DB. Stage 5 - This Really Hurts!: rethink entire application, partition on geography user ID, etc, create user clusters, using hashing scheme for locating which user belongs to which cluster. Stage 6 - Getting a little less painful: scalable application and database architecture, acceptable performance, starting to add ne features again, op
4 0.78506452 383 high scalability-2008-09-10-Shard servers -- go big or small?
Introduction: Hello everyone, I'm designing a website/widget that my business partner and I expect to serve millions of hits daily. As such we must shard our database (and we're designing with shards in mind right from the beginning). However, the one thing I haven't been able to figure out from Googling is the best hardware to go with for shards. I'm using exclusively InnoDB tables. We'll (eventually) be running 3 groups of database servers: a) Session servers for php sessions. These will have a very high write volume. b) ID servers. These will match a couple primary indices (such as user ID) to a given shard. These will have an intense read load, plus a moderate amount of writes. c) Shard servers. These will hold the bulk of the data. These will have a high read load and a lowish write load. Group A is done as a database instead of using memcached so users aren't logged out if a memcached server goes down. As the write load is high, a pair of high performance master-master serv
5 0.78357273 516 high scalability-2009-02-19-Heavy upload server scalability
Introduction: Hi, We are running a backup solution that uploads every night the files our clients worked on during the day (Cabonite-like). We have currently about 10GB of data per night, via http PUT requests (1 per file), and the files are written as-is on a NAS. Our architecture is basically compound of a load balancer (hardware, sticky sessions), 5 servers (Tomcat under RHEL4/5, ) and a NAS (nfs 3). Since our number of clients is rising, (as is our system load) how would you recommend we could scale our infrastructure? hardware and software? Should we go towards NAS sharding, more servers, NIO on tomcat...? Thanks for your inputs!
6 0.77357888 7 high scalability-2007-07-12-FeedBurner Architecture
7 0.77027828 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
8 0.76151502 1329 high scalability-2012-09-26-WordPress.com Serves 70,000 req-sec and over 15 Gbit-sec of Traffic using NGINX
9 0.75350779 68 high scalability-2007-08-20-TypePad Architecture
10 0.75235969 511 high scalability-2009-02-12-MySpace Architecture
11 0.75037444 136 high scalability-2007-10-28-Scaling Early Stage Startups
12 0.74900335 554 high scalability-2009-04-04-Digg Architecture
13 0.74874038 998 high scalability-2011-03-03-Stack Overflow Architecture Update - Now at 95 Million Page Views a Month
14 0.74791813 5 high scalability-2007-07-10-mixi.jp Architecture
15 0.74717736 152 high scalability-2007-11-13-Flickr Architecture
16 0.74262923 1486 high scalability-2013-07-03-5 Rockin' Tips for Scaling PHP to 30,000 Concurrent Users Per Server
17 0.73935068 157 high scalability-2007-11-16-Product: lbpool - Load Balancing JDBC Pool
18 0.73927218 195 high scalability-2007-12-28-Amazon's EC2: Pay as You Grow Could Cut Your Costs in Half
19 0.7380324 513 high scalability-2009-02-16-Handle 1 Billion Events Per Day Using a Memory Grid
20 0.73649305 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
topicId topicWeight
[(1, 0.105), (2, 0.198), (10, 0.1), (11, 0.031), (30, 0.029), (40, 0.022), (47, 0.018), (61, 0.106), (77, 0.014), (79, 0.098), (85, 0.056), (94, 0.056), (99, 0.082)]
simIndex simValue blogId blogTitle
1 0.95478952 478 high scalability-2008-12-29-Paper: Spamalytics: An Empirical Analysisof Spam Marketing Conversion
Introduction: Under the philosophy that the best method to analyse spam is to become a spammer , this absolutely fascinating paper recounts how a team of UC Berkely researchers went under cover to infiltrate a spam network. Part CSI, part Mission Impossible, and part MacGyver, the team hijacked the botnet so that their code was actually part of the dark network itself. Once inside they figured out the architecture and protocols of the botnet and how many sales they were able to tally. Truly elegant work. Two different spam campaigns were run on a Storm botnet network of 75,800 zombie computers. Storm is a peer-to-peer botnet that uses spam to creep its tentacles through the world wide computer network. One of the campains distributed viruses in order to recruit new bots into the network. This is normally accomplished by enticing people to download email attachments. An astonishing one in ten people downloaded the executable and ran it, which means we won't run out of zombies soon. The downloade
same-blog 2 0.95118773 72 high scalability-2007-08-22-Wikimedia architecture
Introduction: Wikimedia is the platform on which Wikipedia, Wiktionary, and the other seven wiki dwarfs are built on. This document is just excellent for the student trying to scale the heights of giant websites. It is full of details and innovative ideas that have been proven on some of the most used websites on the internet. Site: http://wikimedia.org/ Information Sources Wikimedia architecture http://meta.wikimedia.org/wiki/Wikimedia_servers scale-out vs scale-up in the from Oracle to MySQL blog. Platform Apache Linux MySQL PHP Squid LVS Lucene for Search Memcached for Distributed Object Cache Lighttpd Image Server The Stats 8 million articles spread over hundreds of language projects (english, dutch, ...) 10th busiest site in the world (source: Alexa) Exponential growth: doubling every 4-6 months in terms of visitors / traffic / servers 30 000 HTTP requests/s during peak-time 3 Gbit/s of data traffic 3 data centers: Tampa, A
3 0.94164824 1163 high scalability-2011-12-23-Stuff The Internet Says On Scalability For December 23, 2011
Introduction: A merry HighScalability to all and to all a good night: Santa: 3.7 million appointments; iPad2 == 1986 Cray 2 6 processor super computer ; Watson: 200 million pages of natural language content Funny: a cautionary tale about storage and backup . Where is my data? I’m kinda big deal after all! I should have listened to my postdoc, he can build cheaper storage than you can. Nothing stirs up more energy than when someone says they are abandoning and old beloved framework for a newer sexier model. Feelings of betrayal and abandonment leak over everything, which is always a good draw for reality social networking. Here Paul Querna tells why The Switch: Python to Node.js . And here we see the response on Hacker News . Python got the job done for cloudkick, they were acquired, but they wanted something more going forward, a trophy wife if you will, after the first wife put them through law school. Good discussion all around. You may find something that helps in your own platfo
4 0.93893445 1137 high scalability-2011-11-04-Stuff The Internet Says On Scalability For November 4, 2011
Introduction: You're in good hands with HighScalability : Netflix - Cassandra, AWS, 288 instances, 3.3 million writes per second . Quotable quotes: @bretlowery : "A #DBA walks into a #NoSQL bar, but turns and leaves because he couldn't find a table." @AdanVali : HP to Deploy Memristor Powered SSD Replacement Within 18 Months @eden : Ori Lahav: "When planning scalability, think x100, design x5 and deploy x1.5 of current traffic" @jkalucki : If you are IO bound, start with your checkbook! Everything I Ever Learned About JVM Performance Tuning @Twitter . Learn how to tune your Hotspot and other Javasutra secrets. By moving off the cloud Mixipanel may have lost their angel status. Why would they do such a thing? Read Why We Moved Off The Cloud for the details. The reason for the fall: highly variable performance. Highly variable performance is incredibly hard to code or design around (think a server that normally does 300 queries per second with low I/
5 0.93501282 498 high scalability-2009-01-20-Product: Amazon's SimpleDB
Introduction: Update 35 : How and Why Glue is Using Amazon SimpleDB instead of a Relational Database . Discusses a key design decision that required duplicating data in order to mimic RDBMS joins: Given the trade off between potential inconsistencies and scalability, social services have to choose the latter. Update 34 : Apparently Amazon pulled this article. I'm not sure what that means. Maybe time went backwards or something? Amazon dramatically drops SimpleDB pricing to $0.25 per GB per month from $1.50 per GB . This puts SimpleDB on par with Google App Engine . They also announced a few new features: a SQL-like SELECT API as well as a Batch Put operation to streamline uploading of multiple items or attributes . One of the complaints against SimpleDB is that programmers end up writing too much code to do simple things. These features and a much cheaper price should help considerably. And you can store lots of data now. GAE is still capped. Update 33 : Amazon announces
7 0.93136537 1291 high scalability-2012-07-25-Vertical Scaling Ascendant - How are SSDs Changing Architectures?
8 0.93095893 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
9 0.92753577 1171 high scalability-2012-01-09-The Etsy Saga: From Silos to Happy to Billions of Pageviews a Month
10 0.92648792 1382 high scalability-2013-01-07-Analyzing billions of credit card transactions and serving low-latency insights in the cloud
11 0.92478621 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
12 0.92439932 716 high scalability-2009-10-06-Building a Unique Data Warehouse
13 0.92283934 1117 high scalability-2011-09-16-Stuff The Internet Says On Scalability For September 16, 2011
14 0.92256719 374 high scalability-2008-08-30-Paper: GargantuanComputing—GRIDs and P2P
15 0.92240548 907 high scalability-2010-09-23-Working With Large Data Sets
16 0.92209935 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014
17 0.92048985 1600 high scalability-2014-02-21-Stuff The Internet Says On Scalability For February 21st, 2014
18 0.92001539 1642 high scalability-2014-05-02-Stuff The Internet Says On Scalability For May 2nd, 2014
19 0.91971505 1186 high scalability-2012-02-02-The Data-Scope Project - 6PB storage, 500GBytes-sec sequential IO, 20M IOPS, 130TFlops
20 0.91957802 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013