From cce4f7c413eecb4b0bfe9b8bc79c544e4be72111 Mon Sep 17 00:00:00 2001 From: Neil Clifford Date: Fri, 29 Sep 2017 14:16:42 +0100 Subject: [PATCH] Initial re-work of documentation --- docs/CM_FAQs.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CM_FAQs.adoc b/docs/CM_FAQs.adoc index adb2c0d7c..98d6c7138 100755 --- a/docs/CM_FAQs.adoc +++ b/docs/CM_FAQs.adoc @@ -18,7 +18,7 @@ ChronicleMap 3.x. For more information, please refer to Chronicle Engine FAQ's For `get()s`, parallelizing will reduce costs. For `put()s`, if you have concurrency requirements, that is, multi-key lock before updating all of them, it should be in one thread. The stateless client which was available in the last version gives better performance if you use a number of threads. See -https://github.com/OpenHFT/Chronicle-Map#how-to-speed-up-the-chronicle-map-stateless-client +https://github.com/OpenHFT/Chronicle-Map#how-to-speed-up-the-chronicle-map-stateless-client. You would not gain a performance benefit by using batches, unless you are compressing the batch of data. All the data will have to be sent via TCP, even if it's in a batch.