The Economics of Scaling Cassandra - By Alex Bordei, Techie Product Manager at Bigstep
This presentation was made during the "Cassandra Summit 2014" Event, in London.
We benchmarked Cassandra on a number of configurations and we show what's the scaling profile. We test Cassandra on Docker as well as Cassandra's In-memory feature.
Follow Alex on Twitter: @alexandrubordei
Bigstep on Twitter: @BigStepInc
If you have any questions, let us know at hello@bigstep.com and we'll do our best to answer.
Stay informed: http://blog.bigstep.com/
%in Bahrain+277-882-255-28 abortion pills for sale in Bahrain
Cassandra Performance Benchmark
1.
2.
3.
4.
5.
6.
7.
8. Benchmark setup
Centos 6.5, Datastax 4.5.3, jmeter with custom
sampler using the java driver
/dev/shm (100G), HP on, -XX:+UseLargePages,
Disabled THP, IRQBalance
9. Scaling Horizontally - Latency
19
18
16
10 10
9
7
15
7
8
14
7
25
20
15
10
5
0
INSERT AVG response time (us) SELECT AVG response time (us) UPDATE AVG response time (us)
Average response time (ms)
smaller is better
1 node 2 nodes 3 nodes 4 Nodes
20. Memory address translation with and without a TLB
Virtual Address Virtual Address
Physical Address Physical Address
Source:VIRTUAL MEMORY SYSTEMS AND TLB STRUCTURES Univ. Maryland 2001
21. TLB: Translation Lookaside Buffers
• TLB: Translation Lookaside Buffers
• Memory pointers in OS = address in virtual memory not real memory, need an offset to get to the real
memory. Offset needs to be calculated (and this is very expensive) so it is cached in TLB.
• TLB miss normally=150 cycles
• Hardware assisted virtualisation makes normal translation faster in VMs but introduces high penalty on
TLB miss.
22. TLB Misses
Source: “Memory System Characterization of Big Data Workloads” by Martin Dimitrov et al. - Intel Corp. [2013]