mirror of
https://github.com/OpenHFT/Chronicle-Map.git
synced 2021-09-13 01:26:12 +00:00
TeamCity Automatic Merge from master into feature/java11
This commit is contained in:
+39
-2
@@ -1,6 +1,16 @@
|
||||
= Chronicle Map Frequently Asked Questions
|
||||
Neil Clifford, Peter Lawrey, Rob Austin, Jerry Shea
|
||||
:toc: manual
|
||||
:toclevels: 1
|
||||
:css-signature: demo
|
||||
:toc-placement: preamble
|
||||
:icons: font
|
||||
|
||||
== Question
|
||||
This document provides information for some common tasks within Chronicle Map.
|
||||
|
||||
== Can I use Chronicle Map as a replacement of `Redis`, with concurrency in mind?
|
||||
|
||||
===== Question
|
||||
|
||||
I am investigating Chronicle Map as a potential replacement of `Redis`; with concurrency in mind.
|
||||
|
||||
@@ -12,7 +22,7 @@ While I am considering passing off each individual key task to a threadpool runn
|
||||
|
||||
Also, is there a reason these `1000` `gets` have be done serially in one thread? Why not submit `1000 get()` tasks to a pool of say `20` threads. Wouldn't this improve throughput and reduce latency?
|
||||
|
||||
== Answer
|
||||
===== Answer
|
||||
|
||||
The stateless client has been replaced with Chronicle Engine. The stateless client is not supported in ChronicleMap 3.x. For more information, please refer to Chronicle Engine FAQ's.
|
||||
|
||||
@@ -22,5 +32,32 @@ You would not gain a performance benefit by using batches, unless you are compre
|
||||
|
||||
NOTE: Under high load, the Chronicle Map stateless client consolidates many small TCP requests into a single request when run with a number of threads.
|
||||
|
||||
== Does Chronicle Map/Chronicle Queue work by using Memory Mapped Files?
|
||||
|
||||
===== Question
|
||||
Does Chronicle Map work by using Memory Mapped Files?
|
||||
|
||||
===== Answer
|
||||
Yes; Chronicle Map uses memory mapped files see https://en.wikipedia.org/wiki/Memory-mapped_file. This works the same way on both Linux and Windows.
|
||||
|
||||
|
||||
== Is there a difference in performance between Linux and Windows systems?
|
||||
|
||||
===== Question
|
||||
Is there a difference in performance between Linux and Windows systems?
|
||||
|
||||
|
||||
===== Answer
|
||||
The same code is run on both Windows and Linux. However, we encourage all our clients to use Linux, as it has improved handling of memory mapped files over Windows.
|
||||
|
||||
== Will Chronicle Map work in *Docker* environments?
|
||||
|
||||
===== Question
|
||||
Will Chronicle Map work in *Docker* environments “out-of-the-box”. For example, two java programs running on dockers?
|
||||
|
||||
===== Answer
|
||||
While Chronicle Map has not been tested with *Docker*, we are not aware of any reason why it would not if you use Chronicle Map for IPC (https://en.wikipedia.org/wiki/Inter-process_communication). In other words, if you distribute data between two or more instances of the same map, then the same memory mapped file which holds your map data would have to be available to all the instances of Chronicle Map. We assume this would have to be in the same docker. Alternatively, you could replicate the data between your maps using Chronicle Map Enterprise.
|
||||
|
||||
|
||||
'''
|
||||
<<../ReadMe.adoc#,Back to ReadMe>>
|
||||
|
||||
Reference in New Issue
Block a user