One hundred JMeter threads were used to apply the load with 100 connections from JMeter to each node of Cassandra. Each test was run twice to ensure the data was indeed cached, confirmed with iostat. We wanted to test the latency of the client implementation using a single Get Range Slice operation i.e. Total data set is 2.9GB per node so easily cacheable in our instances which have 68GB of memory. Each row has 19 columns of simple ascii data. Six million rows were then inserted into the cluster with a replication factor 3. We set up a simple 6-node Cassandra cluster using EC2 m2.4xlarge instances, and the following schema create keyspace MemberKeySp with placement_strategy = 'NetworkTopologyStrategy' and strategy_options = and durable_writes = true use MemberKeySp create column family Customer with column_type = 'Standard' and comparator = 'UTF8Type' and default_validation_class = 'BytesType' and key_validation_class = 'UTF8Type' and rows_cached = 0.0 and keys_cached = 100000.0 and read_repair_chance = 0.0 and comment = 'Customer Records' The instructions to build and install the jar file are here. It consists of a jar file that is placed in JMeter’s lib/ext directory. The Cassandra JMeter plugin we are releasing today is described on the github wiki here. JMeter allows us to customize our test cases based on our application logic/datamodel. In this blog we discuss the plugin and present performance data for Astyanax vs Thrift collected using this plugin. As Cassandra is a key part of our infrastructure that needs to be tested we developed a JMeter plugin for Cassandra. In January we also announced our Cassandra Java client Astyanax which is built on top of Thrift and provides lower latency, reduced latency variance, and better error handling.Īt Netflix we have recently started to standardize our load testing across the fleet using Apache JMeter. We recently announced the open sourcing of Priam, which is a co-process that runs alongside Cassandra on every node to provide backup and recovery, bootstrapping, token assignment, configuration management and a RESTful interface to monitoring and metrics. It is our plan to open source as much of this software as possible. As part of this move we have not only contributed to Cassandra itself but developed software to ease its deployment and use. We now have over 55 Cassandra clusters in the cloud and are moving our source of truth from our Datacenter to these Cassandra clusters. A number of previous blogs have discussed our adoption of Cassandra as a NoSQL solution in the cloud.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |