[CASSANDRA-6995] Execute local ONE/LOCAL_ONE reads on request thread instead of dispatching to read stage

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Fix Version/s: 2.2.0 beta 1
• Labels: performance
• Assignee: Jason Brown
• Reporter: Jason Brown

Authors

Jason Brown

• Created: 07/Apr/14 22:54
• Updated: 16/Apr/19 09:31
• Resolved: 13/Jun/14 01:44

Description

When performing a read local to a coordinator node, AbstractReadExecutor will create a new SP.LocalReadRunnable and drop it into the read stage for asynchronous execution. If you are using a client that intelligently routes read requests to a node holding the data for a given request, and are using CL.ONE/LOCAL_ONE, the enqueuing SP.LocalReadRunnable and waiting for the context switches (and possible NUMA misses) adds unneccesary latency. We can reduce that latency and improve throughput by avoiding the queueing and thread context switching by simply executing the SP.LocalReadRunnable synchronously in the request thread. Testing on a three node cluster (each with 32 cpus, 132 GB ram) yields ~10% improvement in throughput and ~20% speedup on avg/95/99 percentiles (99.9% was about 5-10% improvement).

Issue Links

• duplicates: CASSANDRA-4718 More-efficient ExecutorService for improved throughput
• is superceded by: CASSANDRA-4718 More-efficient ExecutorService for improved throughput