Added benchmark tests to readme.
diff --git a/benchmarks/single_writer_test.go b/benchmarks/single_writer_test.go
index 9eb35e3..096e20d 100644
--- a/benchmarks/single_writer_test.go
+++ b/benchmarks/single_writer_test.go
@@ -11,7 +11,7 @@
 const singleWriterRingBufferSize = 1024 * 16
 const singleWriterRingBufferMask = singleWriterRingBufferSize - 1
-func BenchmarkDisruptorWriterSingleClaim(b *testing.B) {
+func BenchmarkDisruptorWriterClaimSingle(b *testing.B) {
 	benchmarkSingleWriter(b, 1)
 func BenchmarkDisruptorWriterClaimMultiple(b *testing.B) {
diff --git a/ b/
index a124479..6c3739a 100644
--- a/
+++ b/
@@ -7,6 +7,19 @@
 Once initialized and running, one of the preeminent design considerations of the Disruptor is to produce no garbage thus avoiding the need for GC altogether and to avoid locks at all costs. The current channel implementation maintains a big, fat lock around enqueue/dequeue operations and maxes out on the aforementioned hardware at about 25M messages per second for uncontended access-—more than an order of magnitude slower when compared to the Disruptor.  The same channel, when contended between OS threads (GOMAXPROCS=2 or more) only pushes about 7 million messages per second.
+Scenario | Per Operation Time
+-------- | ------------------ 
+Channel: Non-blocking | 681 ns/op
+Channel: Blocking | 86.6 ns/op|
+Disruptor: SharedWriter (single claim)	| 55.2 ns/op
+Disruptor: SharedWriter (multi claim)	| 2.59 ns/op
+Disruptor: Writer (single claim) | 18.6 ns/op
+Disruptor: Writer (multi claim) | 1.12 ns/op
 When In Doubt, Use Channels
 Despite Go's channels being significantly slower than the Disruptor, channels should still be considered the best and most desirable choice for the vast majority of all use cases. The Disruptor's target use case is ultra-low latency environments where application response times are measured in nanoseconds and where stable, consistent latency is paramount.