high_scalability high_scalability-2007 high_scalability-2007-27 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: 3PAR Remote Copy is a uniquely simple and efficient replication technology that allows customers to protect and share any application data affordably. Built upon 3PAR Thin Copy technology, Remote Copy lowers the total cost of storage by addressing the cost and complexity of remote replication. Common Uses of 3PAR Remote Copy: Affordable Disaster Recovery: Mirror data cost-effectively across town or across the world. Centralized Archive: Replicate data from multiple 3PAR InServs located in multiple data centers to a centralized data archive location. Resilient Pod Architecture: Mutually replicate tier 1 or 2 data to tier 3 capacity between two InServs (application pods). Remote Data Access: Replicate data to a remote location for sharing of data with remote users.
sentIndex sentText sentNum sentScore
1 3PAR Remote Copy is a uniquely simple and efficient replication technology that allows customers to protect and share any application data affordably. [sent-1, score-0.822]
2 Built upon 3PAR Thin Copy technology, Remote Copy lowers the total cost of storage by addressing the cost and complexity of remote replication. [sent-2, score-1.059]
3 Common Uses of 3PAR Remote Copy: Affordable Disaster Recovery: Mirror data cost-effectively across town or across the world. [sent-3, score-0.431]
4 Centralized Archive: Replicate data from multiple 3PAR InServs located in multiple data centers to a centralized data archive location. [sent-4, score-1.078]
5 Resilient Pod Architecture: Mutually replicate tier 1 or 2 data to tier 3 capacity between two InServs (application pods). [sent-5, score-0.858]
6 Remote Data Access: Replicate data to a remote location for sharing of data with remote users. [sent-6, score-1.418]
wordName wordTfidf (topN-words)
[('remote', 0.496), ('inservs', 0.432), ('replicate', 0.299), ('archive', 0.274), ('copy', 0.208), ('tier', 0.172), ('pods', 0.164), ('town', 0.159), ('pod', 0.155), ('mirror', 0.146), ('data', 0.132), ('addressing', 0.132), ('mutually', 0.127), ('affordable', 0.123), ('thin', 0.117), ('uniquely', 0.107), ('protect', 0.105), ('disaster', 0.097), ('centralized', 0.094), ('upon', 0.092), ('technology', 0.091), ('located', 0.089), ('recovery', 0.086), ('cost', 0.084), ('location', 0.084), ('centers', 0.079), ('sharing', 0.078), ('multiple', 0.073), ('across', 0.07), ('total', 0.07), ('complexity', 0.069), ('share', 0.067), ('efficient', 0.062), ('customers', 0.058), ('replication', 0.057), ('application', 0.054), ('capacity', 0.05), ('allows', 0.05), ('uses', 0.045), ('built', 0.044), ('access', 0.042), ('simple', 0.039), ('architecture', 0.033), ('users', 0.033), ('two', 0.033), ('storage', 0.032)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000001 27 high scalability-2007-07-25-Product: 3 PAR REMOTE COPY
Introduction: 3PAR Remote Copy is a uniquely simple and efficient replication technology that allows customers to protect and share any application data affordably. Built upon 3PAR Thin Copy technology, Remote Copy lowers the total cost of storage by addressing the cost and complexity of remote replication. Common Uses of 3PAR Remote Copy: Affordable Disaster Recovery: Mirror data cost-effectively across town or across the world. Centralized Archive: Replicate data from multiple 3PAR InServs located in multiple data centers to a centralized data archive location. Resilient Pod Architecture: Mutually replicate tier 1 or 2 data to tier 3 capacity between two InServs (application pods). Remote Data Access: Replicate data to a remote location for sharing of data with remote users.
2 0.14193365 1467 high scalability-2013-05-30-Google Finds NUMA Up to 20% Slower for Gmail and Websearch
Introduction: When you have a large population of servers you have both the opportunity and the incentive to perform interesting studies. Authors from Google and the University of California in Optimizing Google’s Warehouse Scale Computers: The NUMA Experience conducted such a study, taking a look at how jobs run on clusters of machines using a NUMA architecture. Since NUMA is common on server class machines it's a topic of general interest for those looking to maximize machine utilization across clusters. Some of the results are surprising: The methodology of how to attribute such fine performance variations to NUMA effects within such a complex system is perhaps more interesting than the results themselves. Well worth reading just for that story. The performance swing due to NUMA is up to 15% on AMD Barcelona for Gmail backend and 20% on Intel Westmere for Web-search frontend. Memory locality is not always King. Because of the interaction between NUMA and cache sharing/contention it
3 0.14128883 28 high scalability-2007-07-25-Product: NetApp MetroCluster Software
Introduction: NetApp MetroCluster Software Cost-effective is an integrated high-availability storage cluster and site failover capability. NetApp MetroCluster is an integrated high-availability and disaster recovery solution that can reduce system complexity and simplify management while ensuring greater return on investment. MetroCluster uses clustered server technology to replicate data synchronously between sites located miles apart, eliminating data loss in case of a disruption. Simple and powerful recovery process minimizes downtime, with little or no user action required. At one company I worked at they used the NetApp snap mirror feature to replicate data across long distances to multiple datacenters. They had a very fast backbone and it worked well. The issue with NetApp is always one of cost, but if you can afford it, it's a good option.
4 0.12029576 461 high scalability-2008-12-05-Sprinkle - Provisioning Tool to Build Remote Servers
Introduction: At 37 Signals Joshua Sierles describes how 37 Signals uses Sprinkle to configure their servers within EC2. Sprinkle defines a domain specific meta-language for describing and processing the installation of software . You can find an interesting discussion of Sprinkle's creation story by the creator himself, Marcus Crafter, in Sprinkle Some Powder! . Marcus divides provisioning tools into two categories: Task Based - the tool issues a list of commands to run on the remote system, either remotely via a network connection or smart client. Policy/state Based - the tool determines what needs to be run on the remote system by examining its current and final state. Sprinkle combines both models together in a chocolate-in-my-peanut-butter approach using normal Ruby code as the DSL (domain specific language) to declaratively describe remote system configurations. 37 Signals likes the use of Ruby as the DSL because it makes learning a separate syntax unnecessary. I've successfu
5 0.10878336 1041 high scalability-2011-05-15-Building a Database remote availability site
Introduction: The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. For simplicity, we create a passive redundant site. This means that the site is not used during normal operation and only comes into action when the primary site crashes. There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. The downside is that you have hardware just sitting around doing nothing. Still, it’s a common enough scenario. So what do we need to do to make it work? DATA SYNCHRONIZATION We need to synchronize the database. This is done by means of database replication. Now, there are two options for database replication: synchronous and a-synchronous. Synchronous replication is great; it ensures that the backup database is identical to the
6 0.093384437 163 high scalability-2007-11-21-n-phase commit for FS writes, reads stay local
8 0.084867127 373 high scalability-2008-08-29-Product: ScaleOut StateServer is Memcached on Steroids
9 0.082430393 1316 high scalability-2012-09-04-Changing Architectures: New Datacenter Networks Will Set Your Code and Data Free
10 0.081738994 1521 high scalability-2013-09-23-Salesforce Architecture - How they Handle 1.3 Billion Transactions a Day
11 0.079458646 1529 high scalability-2013-10-08-F1 and Spanner Holistically Compared
12 0.079331689 240 high scalability-2008-02-05-Handling of Session for a site running from more than 1 data center
13 0.07902097 1174 high scalability-2012-01-13-Stuff The Internet Says On Scalability For January 13, 2012
14 0.076934174 688 high scalability-2009-08-26-Hot Links for 2009-8-26
15 0.07362961 1242 high scalability-2012-05-09-Cell Architectures
16 0.07352595 385 high scalability-2008-09-16-Product: Func - Fedora Unified Network Controller
17 0.073389627 1126 high scalability-2011-09-27-Use Instance Caches to Save Money: Latency == $$$
18 0.073110446 329 high scalability-2008-05-27-Secure Remote Administration for Large-Scale Networks
19 0.072168119 1276 high scalability-2012-07-04-Top Features of a Scalable Database
20 0.070675552 297 high scalability-2008-04-05-Skype Plans for PostgreSQL to Scale to 1 Billion Users
topicId topicWeight
[(0, 0.088), (1, 0.019), (2, -0.016), (3, 0.001), (4, -0.032), (5, 0.03), (6, 0.054), (7, -0.052), (8, -0.011), (9, 0.01), (10, 0.009), (11, 0.041), (12, -0.034), (13, -0.009), (14, 0.022), (15, 0.059), (16, -0.003), (17, -0.017), (18, -0.0), (19, 0.023), (20, -0.023), (21, 0.034), (22, 0.004), (23, 0.001), (24, 0.0), (25, 0.001), (26, -0.02), (27, -0.037), (28, 0.009), (29, 0.015), (30, 0.0), (31, -0.026), (32, -0.0), (33, -0.006), (34, -0.034), (35, 0.045), (36, 0.017), (37, 0.021), (38, 0.008), (39, 0.07), (40, 0.009), (41, -0.043), (42, -0.052), (43, 0.019), (44, -0.017), (45, -0.032), (46, -0.036), (47, -0.075), (48, -0.076), (49, 0.009)]
simIndex simValue blogId blogTitle
same-blog 1 0.90485507 27 high scalability-2007-07-25-Product: 3 PAR REMOTE COPY
Introduction: 3PAR Remote Copy is a uniquely simple and efficient replication technology that allows customers to protect and share any application data affordably. Built upon 3PAR Thin Copy technology, Remote Copy lowers the total cost of storage by addressing the cost and complexity of remote replication. Common Uses of 3PAR Remote Copy: Affordable Disaster Recovery: Mirror data cost-effectively across town or across the world. Centralized Archive: Replicate data from multiple 3PAR InServs located in multiple data centers to a centralized data archive location. Resilient Pod Architecture: Mutually replicate tier 1 or 2 data to tier 3 capacity between two InServs (application pods). Remote Data Access: Replicate data to a remote location for sharing of data with remote users.
2 0.74058187 28 high scalability-2007-07-25-Product: NetApp MetroCluster Software
Introduction: NetApp MetroCluster Software Cost-effective is an integrated high-availability storage cluster and site failover capability. NetApp MetroCluster is an integrated high-availability and disaster recovery solution that can reduce system complexity and simplify management while ensuring greater return on investment. MetroCluster uses clustered server technology to replicate data synchronously between sites located miles apart, eliminating data loss in case of a disruption. Simple and powerful recovery process minimizes downtime, with little or no user action required. At one company I worked at they used the NetApp snap mirror feature to replicate data across long distances to multiple datacenters. They had a very fast backbone and it worked well. The issue with NetApp is always one of cost, but if you can afford it, it's a good option.
3 0.71759772 1157 high scalability-2011-12-14-Virtualization and Cloud Computing is Changing the Network to East-West Routing
Introduction: It’s called “east-west” networking, which when compared to its predecessor, “north-south” networking, evinces images of maelstroms and hurricane winds and tsunamis for some reason. It could be the subtle correlation between the transformative shift this change in networking patterns has on the data center with that of El Niño’s transformative power upon the weather patterns across the globe. Traditionally, data center networks have focused on North-South network traffic. The assumption is that clients on the edge would mainly communicate with servers at the core, rather than across the network to other clients. But server virtualization changes all this, with servers, virtual appliances and even virtual desktops scattered across the same physical infrastructure. These environments are also highly dynamic, with workloads moving to different physical locations on the network as virtual servers are migrated (in the case of data center networks) and clients move
4 0.65969431 25 high scalability-2007-07-25-Paper: Designing Disaster Tolerant High Availability Clusters
Introduction: A very detailed (339 pages) paper on how to use HP products to create a highly available cluster. It's somewhat dated and obviously concentrates on HP products, but it is still good information. Table of contents: 1. Disaster Tolerance and Recovery in a Serviceguard Cluster 2. Building an Extended Distance Cluster Using ServiceGuard 3. Designing a Metropolitan Cluster 4. Designing a Continental Cluster 5. Building Disaster-Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access XP 6. Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with EMC SRDF 7. Cascading Failover in a Continental Cluster Evaluating the Need for Disaster Tolerance What is a Disaster Tolerant Architecture? Types of Disaster Tolerant Clusters Extended Distance Clusters Metropolitan Cluster Continental Cluster Continental Cluster With Cascading Failover Disaster Tolerant Architecture Guidelines Protecting Nodes through Geographic Dispersion Protecting Data th
5 0.65179843 809 high scalability-2010-04-13-Strategy: Saving Your Butt With Deferred Deletes
Introduction: Deferred Deletes is a technique where deleted items are marked as deleted but not garbage collected until some days or preferably weeks later . James Hamilton talks describes this strategy in his classic On Designing and Deploying Internet-Scale Services: Never delete anything. Just mark it deleted. When new data comes in, record the requests on the way. Keep a rolling two week (or more) history of all changes to help recover from software or administrative errors. If someone makes a mistake and forgets the where clause on a delete statement (it has happened before and it will again), all logical copies of the data are deleted. Neither RAID nor mirroring can protect against this form of error. The ability to recover the data can make the difference between a highly embarrassing issue or a minor, barely noticeable glitch. For those systems already doing off-line backups, this additional record of data coming into the service only needs to be since the last backup. But, bein
6 0.64807212 822 high scalability-2010-05-04-Business continuity with real-time data integration
7 0.6347366 453 high scalability-2008-12-01-Breakthrough Web-Tier Solutions with Record-Breaking Performance
8 0.63320571 1338 high scalability-2012-10-11-RAMCube: Exploiting Network Proximity for RAM-Based Key-Value Store
9 0.62673604 371 high scalability-2008-08-24-A Scalable, Commodity Data Center Network Architecture
10 0.62235212 128 high scalability-2007-10-21-Paper: Standardizing Storage Clusters (with pNFS)
11 0.61862665 698 high scalability-2009-09-10-Building Scalable Databases: Denormalization, the NoSQL Movement and Digg
12 0.6168561 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
13 0.61485291 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers
14 0.61329561 1316 high scalability-2012-09-04-Changing Architectures: New Datacenter Networks Will Set Your Code and Data Free
15 0.60951728 1570 high scalability-2014-01-01-Paper: Nanocubes: Nanocubes for Real-Time Exploration of Spatiotemporal Datasets
17 0.60445005 1161 high scalability-2011-12-22-Architecting Massively-Scalable Near-Real-Time Risk Analysis Solutions
18 0.60202152 279 high scalability-2008-03-17-Microsoft's New Database Cloud Ready to Rumble with Amazon
19 0.60158283 1578 high scalability-2014-01-14-Ask HS: Design and Implementation of scalable services?
20 0.60149872 1529 high scalability-2013-10-08-F1 and Spanner Holistically Compared
topicId topicWeight
[(1, 0.219), (2, 0.094), (40, 0.508), (79, 0.025)]
simIndex simValue blogId blogTitle
same-blog 1 0.87619394 27 high scalability-2007-07-25-Product: 3 PAR REMOTE COPY
Introduction: 3PAR Remote Copy is a uniquely simple and efficient replication technology that allows customers to protect and share any application data affordably. Built upon 3PAR Thin Copy technology, Remote Copy lowers the total cost of storage by addressing the cost and complexity of remote replication. Common Uses of 3PAR Remote Copy: Affordable Disaster Recovery: Mirror data cost-effectively across town or across the world. Centralized Archive: Replicate data from multiple 3PAR InServs located in multiple data centers to a centralized data archive location. Resilient Pod Architecture: Mutually replicate tier 1 or 2 data to tier 3 capacity between two InServs (application pods). Remote Data Access: Replicate data to a remote location for sharing of data with remote users.
2 0.83338422 338 high scalability-2008-06-02-Total Cost of Ownership for different web development frameworks
Introduction: I would like to compile a comparison matrix on the total cost of ownership for .Net, Java, Lamp & Rails. Where should I start? Has anyone seen or know of a recent study on this subject?
3 0.81988895 402 high scalability-2008-10-05-Paper: Scalability Design Patterns
Introduction: I have introduced pattern languages in my earlier post on The Pattern Bible for Distributed Computing . Achieving highest possible scalability is a complex combination of many factors. This PLoP 2007 paper presents a pattern language that can be used to make a system highly scalable. The Scalability Pattern Language introduced by Kanwardeep Singh Ahluwalia includes patterns to: Introduce Scalability Optimize Algorithm Add Hardware Add Parallelism Add Intra-Process Parallelism Add Inter-Porcess Parallelism Add Hybrid Parallelism Optimize Decentralization Control Shared Resources Automate Scalability
4 0.7984767 1466 high scalability-2013-05-29-Amazon: Creating a Customer Utopia One Culture Hack at a Time
Introduction: If you don’t cannibalize yourself, someone else will. -- Steve Jobs America as the New World has a long history of inspiring Utopian communities . Early experiments were famously religious. But there have been many others as new waves of thought have inspired people to organize and try something different. In the 1840s Transcendentalists, believing the true path lay in the perfection of the individual, created intentional communities like Brook Farm . We've also seen socialist , anarchist , hippy , and virtually every other kind of Utopia in-between. Psychologist B.F. Skinner wrote an infamous book, Walden Two , with a more "scientific" take on creating a Utopian community and Ayn Rand in Atlas Shrugged had her free market version. I believe in startup organizations we see the modern version of Utopian energy in action. We now call it by names like "culture hacking", but the goal is the same: to create a new form of human community to achieve a profound go
5 0.77472669 1419 high scalability-2013-03-07-It's a VM Wasteland - A Near Optimal Packing of VMs to Machines Reduces TCO by 22%
Introduction: In Algorithm Design for Performance Aware VM Consolidation we learn some shocking facts (gambling in Casablanca?): Average server utilization in many data centers is low, estimated between 5% and 15%. This is wasteful because an idle server often consumes more than 50% of peak power. Surely that's just for old style datacenters? Nope. In Google data centers, workloads that are consolidated use only 50% of the processor cores. Every other processor core is left unused simply to ensure that performance does not degrade. It's a VM wasteland. The goal is to reduce waste by packing VMs onto machines without hurting performance or wasting resources. The idea is to select VMs that interfere the least with each other and places them together on the same server. It's a NP-Complete problem, but this paper describes a practical method that performs provably close to the optimal. Interestingly they can optimize for performance or power efficiency, so you can use different algorithm
6 0.75821263 860 high scalability-2010-07-17-Hot Scalability Links for July 17, 2010
7 0.70304662 1414 high scalability-2013-03-01-Stuff The Internet Says On Scalability For February 29, 2013
8 0.70266587 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
10 0.69437343 778 high scalability-2010-02-15-The Amazing Collective Compute Power of the Ambient Cloud
11 0.6813494 848 high scalability-2010-06-25-Hot Scalability Links for June 25, 2010
12 0.6619736 300 high scalability-2008-04-07-Scalr - Open Source Auto-scaling Hosting on Amazon EC2
14 0.65726799 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
15 0.59640491 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
16 0.59331584 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
17 0.59070396 768 high scalability-2010-02-01-What Will Kill the Cloud?
18 0.55623144 97 high scalability-2007-09-18-Session management in highly scalable web sites
19 0.54011542 335 high scalability-2008-05-30-Is "Scaling Engineer" a new job title?
20 0.5370273 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?