DOCSLIB.ORG

Pelikan with ADP Yao Yue (@Thinkingfish), Twitter, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pelikan with ADP Yao Yue (@Thinkingfish), Twitter, Inc Pelikan with ADP Yao Yue (@thinkingfish), Twitter, Inc 1 Pelikan: an Open-sourced, Modular Cache 2 Cache @ Twitter Clusters QPS >400 in prod (single-tenant) max 50M (single cluster) Hosts SLO many thousands p999 < 5ms* Instances Protocol tens of thousands Memcached, Redis/RESP, thrift, … Job size Data Structure 2-6 core, 4-48 GiB Simple KV, counter, list, hash, sorted map... 3 A Modular Architecture Rds Twemcache Slimcache rbuf request response wbuf RESP ... Memcache Memcache SArray,List,.. Slab Cuckoo Slab services parse process compose ziplist sarray memcache admin bitmap ... Data Data data structure RESP ... Structure Store slab cuckoo datastore protocols process_request(struct response **, struct request *); High-performance rpc server 4 Intel® Optane™ Pelikan DC Persistent Memory 5 Intel® Optane™ DC Persistent Memory MEMORY MODE APP DIRECT APPLICATION APPLICATION VOLATILE MEMORY POOL DRAM AS CACHE OPTANE PERSISTENT MEMORY DRAM OPTANE PERSISTENT MEMORY Affordable, large volatile Large capacity persistent memory capacity memory No code changes 6 Pelikan with Apache Pass (AEP) Motivation Constraints Cache more data per instance Maintainable Changes ➔ Reduce TCO if memory-bound ➔ Same codebase ➔ Improve hit rate ➔ Non-invasive, retain high-level APIs Persistent data => warmer cache Operability ➔ Improve operations w/ graceful shutdown and faster rebuild ➔ Flexible invocation Predictable performance ➔ Higher availability during ➔ maintenance 7 Data Pool Abstraction with PMDK slab cuckoo datastore Persistent Persistenc Memory e w/ slab cuckoo (file- libpmem backed) (PMDK) Datapool datastore “cc_alloc” DRAM (malloc) 8 Durable Storage with DRAM Compatibility Cuckoo Slab bucket bucket hash table slabs PMEMDRAM 9 Results 10 Benchmark Overview Core Parameters Focus Instance density 18-30 instances / host common ➔ Serving performance (vs. DRAM) Object size Perf scalability with different dataset Between 64 and 2048 bytes, step x2 ➔ size Dataset size Between 4GiB and 32 GiB / instance, step x2 app direct mode # of Connection per Server ➔ Rebuild performance 100 / 1000 app direct vs memory mode R/W ratio Read-only, 90/10, 80/20 Lab vs data center Twemcache-only for this presentation Bottleneck analysis 11 Stage 1: Serving Performance (memory mode) (aka “does this work at all?”) 4 GiB (throughput) 1600 Hardware Config (Intel lab) 4 GiB (latency) 3M · 2 X Intel Xeon 8160 (24) 1400 · 12 X 32GB DIMM 8 GiB (throughput) · 12 X 128GB AEP 8 GiB (latency) 2.5M 1200 · 2-2-2 config ) 16 GiB (throughput) us · 1 X 25Gb NIC , 16 GiB (latency) 2M 1000 · CentOS 7 999 p 32 GiB (throughput) ( Test Config QPS 800 32 GiB (latency) 1.5M · 30 instances per node 600 · key size is 32 byte Latency 1M · connection count is 100 400 · NUMA-aware · 90 R / 10 W 0.5M 200 0 0 64 128 256 512 1024 2048 Value Size 12 Stage 2: Serving Performance (app direct mode) 4 GiB (throughput) 2M 200 Hardware Config (Intel lab) 4 GiB (latency) · 2 X Intel Xeon 8260 (24) · 12 X 32GB DIMM 8 GiB (throughput) · 12 X 128GB AEP 8 GiB (latency) 150 · 2-2-2 config 1.5M ) 16 GiB (throughput) us · 1 X 25Gb NIC 16 GiB (latency) , · CentOS 7 999 p 32 GiB (throughput) ( Test Config QPS 1M 100 32 GiB (latency) · 24 instances per node · key size is 32 byte Latency · connection count is 100 0.5M 50 · NUMA-aware 0 0 64 128 256 512 1024 Value Size 13 Stage 2: Recovery Performance Status Quo Rebuild from AEP Data Availability Single instance ➔ No redundancy in cache by default ➔ 100 GiB of slab data ➔ Some clusters are mirrored ➔ complete rebuild: 4 minutes Backfill Concurrent ➔ Mostly rely on organic traffic ➔ 18 instances per host ➔ “Bootstrapper” bounded by QPS ➔ complete rebuild: 5 minutes Full warmup takes from minutes to ➔ Potential impact days ➔ Speed up maintenance by 1-2 orders Constraints on maintenance of magnitude (often needs other ➔ 20 minute restart interval by default changes) ➔ Large clusters take days to restart 14 Stage 3: Testing In-house (memory mode) 2 keys: 10M / 4GiB Hardware Config (Twitter DC) keys: 20M / 9GiB 100k · 2 X Intel Xeon 6222 (20) keys: 40M / 18GiB · 12 X 16GB DIMM 5 keys: 80M / 37GiB · 4 X 512GB AEP keys: 160M / 74GiB 2 · 2-1-1 config · 1 X 25Gb NIC ) 10k · CentOS 7 us SLO: p999 < 5ms ( 5 Test Config 2 · 20 instances per node Latency · key size is 64 byte 1000 · value size is 256 byte 5 · connection count is 1000 · NUMA-aware 2 · read-only p999 max = 16ms p9999 max = 148ms 100 p25 p50 p75 p90 p99 p999 p9999 throughput 1.08M QPS Percentile 15 Stage 3: Testing In-house (app direct mode) 2 keys: 10M / 4GiB Hardware Config (Twitter DC) keys: 20M / 9GiB 100k · 2 X Intel Xeon 6222 (20) keys: 40M / 18GiB · 12 X 16GB DIMM 5 keys: 80M / 37GiB · 4 X 512GB AEP keys: 160M / 74GiB 2 · 2-1-1 config · 1 X 25Gb NIC ) 10k · CentOS 7 us SLO: p999 < 5ms ( 5 Test Config 2 · 20 instances per node Latency · key size is 64 byte 1000 · value size is 256 byte 5 · connection count is 1000 · NUMA-aware 2 · read-only p999 max = 1.4ms p9999 max = 2.5ms 100 p25 p50 p75 p90 p99 p999 p9999 throughput 1.08M QPS Percentile 16 Conclusion Next Step App direct mode Network ● Changes were modest ● Testing in-house with ADQ ● Can serve all data structures ● Serving performance comparable to Production canary DRAM for tested Twitter workloads ● Will we see the same performance? ● Recovery performance was good ● How does larger heap affect hit rate? Memory mode ● Fully-loaded config performs like Performance DRAM ● Scaling with connection counts ● Less scalable w/ wimpier config ● Profiling, especially for memory mode Bottleneck ● Tuning data structure/storage ● Network is still primary design ● Testing AEP with pelikan_rds 17 Further Read Contributors Pelikan Thank you Intel Team! ● Redis at Scale Ali Alavi (@TheAliAlavi), Andy Rudoff ● Caching with Twemcache (@andyrudoff), Jakub Schmiegel, Jason ● Why Pelikan Harper, Michal Biesek, Mauricio Cuervo ● Pelikan Github (@mauriciocuervo), Piotr Balcer, Usha Upadhyayula Cache w/ AEP ● Redis-pmem Thank you Twitter Team! ● Memcached with pmem Brian Martin (@brayniac), Kevin Yang (@kevjyang), Matt Silver (@msilver) #collaborate 18.
Load more

Recommended publications
  • Redis and Memcached
    Redis and Memcached Speaker: Vladimir Zivkovic, Manager, IT June, 2019 Problem Scenario • Web Site users wanting to access data extremely quickly (< 200ms) • Data being shared between different layers of the stack • Cache a web page sessions • Research and test feasibility of using Redis as a solution for storing and retrieving data quickly • Load data into Redis to test ETL feasibility and Performance • Goal - get sub-second response for API calls for retrieving data !2 Why Redis • In-memory key-value store, with persistence • Open source • Written in C • It can handle up to 2^32 keys, and was tested in practice to handle at least 250 million of keys per instance.” - http://redis.io/topics/faq • Most popular key-value store - http://db-engines.com/en/ranking !3 History • REmote DIctionary Server • Released in 2009 • Built in order to scale a website: http://lloogg.com/ • The web application of lloogg was an ajax app to show the site traffic in real time. Needed a DB handling fast writes, and fast ”get latest N items” operation. !4 Redis Data types • Strings • Bitmaps • Lists • Hyperlogs • Sets • Geospatial Indexes • Sorted Sets • Hashes !5 Redis protocol • redis[“key”] = “value” • Values can be strings, lists or sets • Push and pop elements (atomic) • Fetch arbitrary set and array elements • Sorting • Data is written to disk asynchronously !6 Memory Footprint • An empty instance uses ~ 3MB of memory. • For 1 Million small Keys => String Value pairs use ~ 85MB of memory. • 1 Million Keys => Hash value, representing an object with 5 fields,
    [Show full text]
  • Modeling and Analyzing Latency in the Memcached System
    Modeling and Analyzing Latency in the Memcached system Wenxue Cheng1, Fengyuan Ren1, Wanchun Jiang2, Tong Zhang1 1Tsinghua National Laboratory for Information Science and Technology, Beijing, China 1Department of Computer Science and Technology, Tsinghua University, Beijing, China 2School of Information Science and Engineering, Central South University, Changsha, China March 27, 2017 abstract Memcached is a widely used in-memory caching solution in large-scale searching scenarios. The most pivotal performance metric in Memcached is latency, which is affected by various factors including the workload pattern, the service rate, the unbalanced load distribution and the cache miss ratio. To quantitate the impact of each factor on latency, we establish a theoretical model for the Memcached system. Specially, we formulate the unbalanced load distribution among Memcached servers by a set of probabilities, capture the burst and concurrent key arrivals at Memcached servers in form of batching blocks, and add a cache miss processing stage. Based on this model, algebraic derivations are conducted to estimate latency in Memcached. The latency estimation is validated by intensive experiments. Moreover, we obtain a quantitative understanding of how much improvement of latency performance can be achieved by optimizing each factor and provide several useful recommendations to optimal latency in Memcached. Keywords Memcached, Latency, Modeling, Quantitative Analysis 1 Introduction Memcached [1] has been adopted in many large-scale websites, including Facebook, LiveJournal, Wikipedia, Flickr, Twitter and Youtube. In Memcached, a web request will generate hundreds of Memcached keys that will be further processed in the memory of parallel Memcached servers. With this parallel in-memory processing method, Memcached can extensively speed up and scale up searching applications [2].
    [Show full text]
  • Release 2.5.5 Ask Solem Contributors
    Celery Documentation Release 2.5.5 Ask Solem Contributors February 04, 2014 Contents i ii Celery Documentation, Release 2.5.5 Contents: Contents 1 Celery Documentation, Release 2.5.5 2 Contents CHAPTER 1 Getting Started Release 2.5 Date February 04, 2014 1.1 Introduction Version 2.5.5 Web http://celeryproject.org/ Download http://pypi.python.org/pypi/celery/ Source http://github.com/celery/celery/ Keywords task queue, job queue, asynchronous, rabbitmq, amqp, redis, python, webhooks, queue, dis- tributed – • Synopsis • Overview • Example • Features • Documentation • Installation – Bundles – Downloading and installing from source – Using the development version 1.1.1 Synopsis Celery is an open source asynchronous task queue/job queue based on distributed message passing. Focused on real- time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background) or synchronously (wait until ready). Celery is used in production systems to process millions of tasks every hour. 3 Celery Documentation, Release 2.5.5 Celery is written in Python, but the protocol can be implemented in any language. It can also operate with other languages using webhooks. There’s also RCelery for the Ruby programming language, and a PHP client. The recommended message broker is RabbitMQ, but support for Redis, MongoDB, Beanstalk, Amazon SQS, CouchDB and databases (using SQLAlchemy or the Django ORM) is also available. Celery is easy to integrate with web frameworks, some of which even have integration packages: Django django-celery Pyramid pyramid_celery Pylons celery-pylons Flask flask-celery web2py web2py-celery 1.1.2 Overview This is a high level overview of the architecture.
    [Show full text]
  • An End-To-End Application Performance Monitoring Tool
    Applications Manager - an end-to-end application performance monitoring tool For enterprises to stay ahead of the technology curve in today's competitive IT environment, it is important for their business critical applications to perform smoothly. Applications Manager - ManageEngine's on-premise application performance monitoring solution offers real-time application monitoring capabilities that offer deep visibility into not only the performance of various server and infrastructure components but also other technologies used in the IT ecosystem such as databases, cloud services, virtual systems, application servers, web server/services, ERP systems, big data, middleware and messaging components, etc. Highlights of Applications Manager Wide range of supported apps Monitor 150+ application types and get deep visibility into all the components of your application environment. Ensure optimal performance of all your applications by visualizing real-time data via comprehensive dashboards and reports. Easy installation and setup Get Applications Manager running in under two minutes. Applications Manager is an agentless monitoring tool and it requires no complex installation procedures. Automatic discovery and dependency mapping Automatically discover all applications and servers in your network and easily categorize them based on their type (apps, servers, databases, VMs, etc.). Get comprehensive insight into your business infrastructure, drill down to IT application relationships, map them effortlessly and understand how applications interact with each other with the help of these dependency maps. Deep dive performance metrics Track key performance metrics of your applications like response times, requests per minute, lock details, session details, CPU and disk utilization, error states, etc. Measure the efficiency of your applications by visualizing the data at regular periodic intervals.
    [Show full text]
  • WEB2PY Enterprise Web Framework (2Nd Edition)
    WEB2PY Enterprise Web Framework / 2nd Ed. Massimo Di Pierro Copyright ©2009 by Massimo Di Pierro. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the web at www.copyright.com. Requests to the Copyright owner for permission should be addressed to: Massimo Di Pierro School of Computing DePaul University 243 S Wabash Ave Chicago, IL 60604 (USA) Email: [email protected] Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created ore extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages. Library of Congress Cataloging-in-Publication Data: WEB2PY: Enterprise Web Framework Printed in the United States of America.
    [Show full text]
  • Performance at Scale with Amazon Elasticache
    Performance at Scale with Amazon ElastiCache July 2019 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 ElastiCache Overview ......................................................................................................... 2 Alternatives to ElastiCache ................................................................................................. 2 Memcached vs. Redis ......................................................................................................... 3 ElastiCache for Memcached ............................................................................................... 5 Architecture with ElastiCache for Memcached ...............................................................
    [Show full text]
  • High Performance with Distributed Caching
    High Performance with Distributed Caching Key Requirements For Choosing The Right Solution High Performance with Distributed Caching: Key Requirements for Choosing the Right Solution Table of Contents Executive summary 3 Companies are choosing Couchbase for their caching layer, and much more 3 Memory-first 4 Persistence 4 Elastic scalability 4 Replication 5 More than caching 5 About this guide 5 Memcached and Oracle Coherence – two popular caching solutions 6 Oracle Coherence 6 Memcached 6 Why cache? Better performance, lower costs 6 Common caching use cases 7 Key requirements for an effective distributed caching solution 8 Problems with Oracle Coherence: cost, complexity, capabilities 8 Memcached: A simple, powerful open source cache 10 Lack of enterprise support, built-in management, and advanced features 10 Couchbase Server as a high-performance distributed cache 10 General-purpose NoSQL database with Memcached roots 10 Meets key requirements for distributed caching 11 Develop with agility 11 Perform at any scale 11 Manage with ease 12 Benchmarks: Couchbase performance under caching workloads 12 Simple migration from Oracle Coherence or Memcached to Couchbase 13 Drop-in replacement for Memcached: No code changes required 14 Migrating from Oracle Coherence to Couchbase Server 14 Beyond caching: Simplify IT infrastructure, reduce costs with Couchbase 14 About Couchbase 14 Caching has become Executive Summary a de facto technology to boost application For many web, mobile, and Internet of Things (IoT) applications that run in clustered performance as well or cloud environments, distributed caching is a key requirement, for reasons of both as reduce costs. performance and cost. By caching frequently accessed data in memory – rather than making round trips to the backend database – applications can deliver highly responsive experiences that today’s users expect.
    [Show full text]
  • Opinnäytetyön Malli Vanhoille Word-Versioille
    Bachelor’s Thesis Information Technology 2011 Kenneth Emeka Odoh DESIGN AND IMPLEMENTATION OF A WEB- BASED AUCTION SYSTEM ii BACHELOR’S THESIS (UAS) │ABSTRACT TURKU UNIVERSITY OF APPLIED SCIENCES Information Technology | Networking Date of completion of the thesis | 12th January 2012 Instructor: Ferm Tiina Kenneth Emeka Odoh DESIGN AND IMPLEMENTATION OF A WEB- BASED AUCTION SYSTEM Electronic auction has been a popular means of goods distribution. The number of items sold through the internet auction sites have grown in the past few years. Evidently, this has become the medium of choice for customers. This project entails the design and implementation of a web-based auction system for users to trade in goods. The system was implemented in the Django framework. On account that the trade over the Internet lacks any means of ascertaining the quality of goods, there is a need to implement a feedback system to rate the seller’s credibility in order to increase customer confidence in a given business. The feedback system is based on the history of the customer’s rating of the previous seller’s transactions. As a result, the auction system has a built-in feedback system to enhance the credibility of the auction system. The project was designed by using a modular approach to ensure maintainability. There is a number of engines that were implemented in order to enhance the functionality of the auction system. They include the following: commenting engine, search engine, business intelligence (user analytic and statistics), graph engine, advertisement engine and recommendation engine. As a result of this thesis undertaking, a full-fledged system robust enough to handle small or medium-sized traffic has been developed to specification.
    [Show full text]
  • VSI's Open Source Strategy
    VSI's Open Source Strategy Plans and schemes for Open Source so9ware on OpenVMS Bre% Cameron / Camiel Vanderhoeven April 2016 AGENDA • Programming languages • Cloud • Integraon technologies • UNIX compability • Databases • Analy;cs • Web • Add-ons • Libraries/u;li;es • Other consideraons • SoDware development • Summary/conclusions tools • Quesons Programming languages • Scrip;ng languages – Lua – Perl (probably in reasonable shape) – Tcl – Python – Ruby – PHP – JavaScript (Node.js and friends) – Also need to consider tools and packages commonly used with these languages • Interpreted languages – Scala (JVM) – Clojure (JVM) – Erlang (poten;ally a good fit with OpenVMS; can get good support from ESL) – All the above are seeing increased adop;on 3 Programming languages • Compiled languages – Go (seeing rapid adop;on) – Rust (relavely new) – Apple Swi • Prerequisites (not all are required in all cases) – LLVM backend – Tweaks to OpenVMS C and C++ compilers – Support for latest language standards (C++) – Support for some GNU C/C++ extensions – Updates to OpenVMS C RTL and threads library 4 Programming languages 1. JavaScript 2. Java 3. PHP 4. Python 5. C# 6. C++ 7. Ruby 8. CSS 9. C 10. Objective-C 11. Perl 12. Shell 13. R 14. Scala 15. Go 16. Haskell 17. Matlab 18. Swift 19. Clojure 20. Groovy 21. Visual Basic 5 See h%p://redmonk.com/sogrady/2015/07/01/language-rankings-6-15/ Programming languages Growing programming languages, June 2015 Steve O’Grady published another edi;on of his great popularity study on programming languages: RedMonk Programming Language Rankings: June 2015. As usual, it is a very valuable piece. There are many take-away from this research.
    [Show full text]
  • Amazon Elasticache Deep Dive Powering Modern Applications with Low Latency and High Throughput
    Amazon ElastiCache Deep Dive Powering modern applications with low latency and high throughput Michael Labib Sr. Manager, Non-Relational Databases © 2020, Amazon Web Services, Inc. or its Affiliates. Agenda • Introduction to Amazon ElastiCache • Redis Topologies & Features • ElastiCache Use Cases • Monitoring, Sizing & Best Practices © 2020, Amazon Web Services, Inc. or its Affiliates. Introduction to Amazon ElastiCache © 2020, Amazon Web Services, Inc. or its Affiliates. Purpose-built databases © 2020, Amazon Web Services, Inc. or its Affiliates. Purpose-built databases © 2020, Amazon Web Services, Inc. or its Affiliates. Modern real-time applications require Performance, Scale & Availability Users 1M+ Data volume Terabytes—petabytes Locality Global Performance Microsecond latency Request rate Millions per second Access Mobile, IoT, devices Scale Up-out-in E-Commerce Media Social Online Shared economy Economics Pay-as-you-go streaming media gaming Developer access Open API © 2020, Amazon Web Services, Inc. or its Affiliates. Amazon ElastiCache – Fully Managed Service Redis & Extreme Secure Easily scales to Memcached compatible performance and reliable massive workloads Fully compatible with In-memory data store Network isolation, encryption Scale writes and open source Redis and cache for microsecond at rest/transit, HIPAA, PCI, reads with sharding and Memcached response times FedRAMP, multi AZ, and and replicas automatic failover © 2020, Amazon Web Services, Inc. or its Affiliates. What is Redis? Initially released in 2009, Redis provides: • Complex data structures: Strings, Lists, Sets, Sorted Sets, Hash Maps, HyperLogLog, Geospatial, and Streams • High-availability through replication • Scalability through online sharding • Persistence via snapshot / restore • Multi-key atomic operations A high-speed, in-memory, non-Relational data store. • LUA scripting Customers love that Redis is easy to use.
    [Show full text]
  • Developing Replication Plugins for Drizzle
    Developing Replication Plugins for Drizzle Jay Pipes [email protected] http://joinfu.com Padraig O'Sullivan [email protected] http://posulliv.com These slides released under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License what we'll cover today Contributing to Drizzle Overview of Drizzle's architecture Code walkthrough of Drizzle plugin basics Overview of Drizzle's replication system Understanding Google Protobuffers The Transaction message In depth walkthrough of the filtered replicator In-depth walkthrough of the transaction log The future, your ideas, making an impact Drizzle is a Community Being a Drizzler Some things to remember... No blame No shame Be open and transparent Learn something from someone? Pass it on... − By adding to the wiki (http://drizzle.org/wiki/) − By sharing it with another contributor − By blogging about it − By posting what you learn to the mailing list There is no such thing as a silly question NO TROLLS. Managing Your Code Launchpad and BZR Launchpad.net The Drizzle community focal-point − http://launchpad.net/drizzle Join the drizzle-developers team: − http://launchpad.net/~drizzle-developers − Once on the team, you'll be able to push BZR branches to the main Drizzle code repository Launchpad.net Code management Task (blueprint) management Bug reporting Translations (Rosetta) FAQ functionality − http://www.joinfu.com/2008/08/a-contributors-guide- to-launchpadnet-part-1-getting-started/ − http://www.joinfu.com/2008/08/a-contributors-guide- to-launchpadnet-part-2-code-management/
    [Show full text]
  • Designing and Implementing Scalable Applications with Memcached and Mysql
    Designing and Implementing Scalable Applications with Memcached and MySQL A MySQL ® White Paper June, 2008 Copyright © 2008, MySQL AB Table of Contents Designing and Implementing ........................................................................................................... 1 Scalable Applications with Memcached and MySQL ................................................................ 1 Table of Contents ................................................................................................................................... 2 Introduction ............................................................................................................................................. 3 Memcached Overview .......................................................................................................................... 3 How Memcached Works ...................................................................................................................... 4 Memcached Server ................................................................................................................................ 5 Memcached Clients ............................................................................................................................... 8 Example Architectures ......................................................................................................................... 9 Solutions: Memcached for MySQL ................................................................................................
    [Show full text]