Release 2.5.5 Ask Solem Contributors

Total Page:16

File Type:pdf, Size:1020Kb

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. The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on the workload. The result of the task can be stored for later retrieval (called its “tombstone”). 1.1.3 Example You probably want to see some code by now, so here’s an example task adding two numbers: from celery.task import task @task def add(x, y): return x + y You can execute the task in the background, or wait for it to finish: >>> result = add.delay(4,4) >>> result.wait() # wait for and return the result 8 Simple! 4 Chapter 1. Getting Started Celery Documentation, Release 2.5.5 1.1.4 Features Mes- Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and saging popular SQL databases. Fault- Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never tolerant lost. Dis- Runs on one or more machines. Supports broker clustering andHA when used in tributed combination with RabbitMQ. You can set up new workers without central configuration (e.g. use your grandma’s laptop to help if the queue is temporarily congested). Concur- Concurrency is achieved by using multiprocessing, Eventlet, gevent or a mix of these. rency Schedul- Supports recurring tasks like cron, or specifying an exact date or countdown for when ing after the task should be executed. Latency Low latency means you are able to execute tasks while the user is waiting. Return Task return values can be saved to the selected result store backend. You can wait for the Values result, retrieve it later, or ignore it. Result Database, MongoDB, Redis, Cassandra, or AMQP (message notification). Stores Web- Your tasks can also be HTTP callbacks, enabling cross-language communication. hooks Rate Supports rate limiting by using the token bucket algorithm, which accounts for bursts of limiting traffic. Rate limits can be set for each task type, or globally for all. Routing Using AMQP’s flexible routing model you can route tasks to different workers, or select different message topologies, by configuration or even at runtime. Remote- Worker nodes can be controlled from remote by using broadcast messaging. A range of control built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Moni- You can capture everything happening with the workers in real-time by subscribing to toring events. A real-time web monitor is in development. Serial- Supports Pickle, JSON, YAML, or easily defined custom schemes. One task invocation ization can have a different scheme than another. Trace- Errors and tracebacks are stored and can be investigated after the fact. backs UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return value. Retries Tasks can be retried if they fail, with configurable maximum number of retries, and delays between each retry. Task A Task set is a task consisting of several sub-tasks. You can find out how many, or if all of Sets the sub-tasks has been executed, and even retrieve the results in order. Progress bars, anyone? Made You can query status and results via URLs, enabling the ability to poll task status using for Web Ajax. Error Can be configured to send emails to the administrators when tasks fails. Emails 1.1.5 Documentation Documentation for the production version can be found here: http://docs.celeryproject.org/en/latest and the documentation for the development version can be found here: http://celery.github.com/celery/ 1.1. Introduction 5 Celery Documentation, Release 2.5.5 1.1.6 Installation You can install Celery either via the Python Package Index (PyPI) or from source. To install using pip,: $ pip install -U Celery To install using easy_install,: $ easy_install -U Celery Bundles Celery also defines a group of bundles that can be used to install Celery and the dependencies for a given feature. The following bundles are available: celery-with-redis for using Redis as a broker. celery-with-mongodb for using MongoDB as a broker. django-celery-with-redis for Django, and using Redis as a broker. django-celery-with-mongodb for Django, and using MongoDB as a broker. bundle-celery convenience bundle installing Celery and related packages. Downloading and installing from source Download the latest version of Celery from http://pypi.python.org/pypi/celery/ You can install it by doing the following,: $ tar xvfz celery-0.0.0.tar.gz $ cd celery-0.0.0 $ python setup.py build # python setup.py install # as root Using the development version You can clone the repository by doing the following: $ git clone git://github.com/celery/celery.git 1.2 Brokers Release 2.5 Date February 04, 2014 Celery supports several message transport alternatives. 6 Chapter 1. Getting Started Celery Documentation, Release 2.5.5 1.2.1 Using RabbitMQ • Installation & Configuration • Installing the RabbitMQ Server – Setting up RabbitMQ – Installing RabbitMQ on OS X * Configuring the system host name * Starting/Stopping the RabbitMQ server Installation & Configuration RabbitMQ is the default broker so it does not require any additional dependencies or initial configuration, other than the URL location of the broker instance you want to use: >>> BROKER_URL = "amqp://guest:guest@localhost:5672//" For a description of broker URLs and a full list of the various broker configuration options available to Celery, see Broker Settings. Installing the RabbitMQ Server See Installing RabbitMQ over at RabbitMQ’s website. For Mac OS X see Installing RabbitMQ on OS X. Note: If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ Setting up RabbitMQ To use celery we need to create a RabbitMQ user, a virtual host and allow that user access to that virtual host: $ rabbitmqctl add_user myuser mypassword $ rabbitmqctl add_vhost myvhost $ rabbitmqctl set_permissions -p myvhost myuser ".*" ".*" ".*" See the RabbitMQ Admin Guide for more information about access control. Installing RabbitMQ on OS X The easiest way to install RabbitMQ on Snow Leopard is using Homebrew; the new and shiny package management system for OS X. In this example we’ll install Homebrew into /lol, but you can choose whichever destination, even in your home directory if you want, as one of the strengths of Homebrew is that it’s relocatable. Homebrew is actually a git repository, so to install Homebrew, you first need to install git. Download and install from the disk image at http://code.google.com/p/git-osx-installer/downloads/list?can=3 When git is installed you can finally clone the repository, storing it at the /lol location: 1.2. Brokers 7 Celery Documentation, Release 2.5.5 $ git clone git://github.com/mxcl/homebrew /lol Brew comes with a simple utility called brew, used to install, remove and query packages. To use it you first have to add it to PATH, by adding the following line to the end of your ~/.profile: export PATH="/lol/bin:/lol/sbin:$PATH" Save your profile and reload it: $ source ~/.profile Finally, we can install rabbitmq using brew: $ brew install rabbitmq Configuring the system host name If you’re using a DHCP server that is giving you a random host name, you need to permanently configure the host name. This is because RabbitMQ uses the host name to communicate with nodes. Use the scutil command to permanently set your host name: sudo scutil --set HostName myhost.local Then add that host name to /etc/hosts so it’s possible to resolve it back into an IP address: 127.0.0.1 localhost myhost myhost.local If you start the rabbitmq server, your rabbit node should now be rabbit@myhost, as verified by rabbitmqctl: $ sudo rabbitmqctl status Status of node rabbit@myhost ... [{running_applications,[{rabbit,"RabbitMQ","1.7.1"}, {mnesia,"MNESIA CXC 138 12","4.4.12"}, {os_mon,"CPO CXC 138 46","2.2.4"}, {sasl,"SASL CXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done.
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]
  • 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]
  • Memcached, Redis, and Aerospike Key-Value Stores Empirical
    Memcached, Redis, and Aerospike Key-Value Stores Empirical Comparison Anthony Anthony Yaganti Naga Malleswara Rao University of Waterloo University of Waterloo 200 University Ave W 200 University Ave W Waterloo, ON, Canada Waterloo, ON, Canada +1 (226) 808-9489 +1 (226) 505-5900 [email protected] [email protected] ABSTRACT project. Thus, the results are somewhat biased as the tested DB The popularity of NoSQL database and the availability of larger setup might be set to give more advantage of one of the systems. DRAM have generated a great interest in in-memory key-value We will discuss more in Section 8 (Related Work). stores (kv-store) in the recent years. As a consequence, many In this work, we conduct a thorough experimental evaluation by similar kv-store store projects/products has emerged. Besides the comparing three major key-value stores nowadays, namely Redis, benchmarking results provided by the KV-store developers which Memcached, and Aerospike. We first elaborate the databases that are usually tested under their favorable setups and scenario, there we tested in Section 3. Then, the evaluation methodology are very limited comprehensive resources for users to decide comprises experimental setups, i.e., single and cluster mode; which kv-store to choose given a specific workload/use-case. To benchmark setups including the description of YCSB, dataset provide users with an unbiased and up-to-date insight in selecting configurations, types workloads (i.e., read-heavy, balanced, in-memory kv-stores, we conduct a study to empirically compare write-heavy), and concurrent access; and evaluation metrics will Redis, Memcached and Aerospike on equal ground by trying to be discussed in Section 4.
    [Show full text]