Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

Initial re-work of documentation

Browse Source
This commit is contained in:
Neil Clifford
2017-09-29 14:16:42 +01:00
parent 3f291a2a6d
commit cce4f7c413
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CM_FAQs.adoc
+1 -1
View File
@@ -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>
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.