You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document Chronicle Map architecture & system properties; tidy APIs, quality rules, and tests (#580)
* removing obsolete doclint suppression from the Maven Javadoc configuration
* expanding targeted Checkstyle suppressions for legacy/test-only sources
* cleaning up unused imports, whitespace, comments, and assertion style
* applying final and clearer variable names where useful
* removing redundant checked exceptions from method signatures
* adding explicit braces and switch defaults for clearer control flow
Copy file name to clipboardExpand all lines: docs/CM_Features.adoc
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,16 @@ Neil Clifford
5
5
:css-signature: demo
6
6
:toc-placement: macro
7
7
:icons: font
8
+
:lang: en-GB
9
+
:source-highlighter: rouge
8
10
9
11
toc::[]
10
12
11
13
Chronicle Map is an in-memory, key-value store, designed for low-latency, and/or multi-process applications, such as trading and financial market applications.
12
14
13
15
== Features
14
16
15
-
- **Ultra low latency**: Chronicle Map targets median latency of both read and write queries of less than 1 microsecond in https://github.com/OpenHFT/Chronicle-Map/search?l=java&q=perf&type=Code[certain tests].
17
+
- **Ultra low latency**: Chronicle Map targets median latency of both read and write queries of less than 1 µs in https://github.com/OpenHFT/Chronicle-Map/search?l=java&q=perf&type=Code[certain tests].
16
18
17
19
- **High concurrency**: Write queries scale well up to the number of hardware execution threads in the server.
18
20
Read queries never block each other.
@@ -23,7 +25,7 @@ Read queries never block each other.
23
25
24
26
- Multiple processes can access a Chronicle Map concurrently.
25
27
At the same time, the data store is *in-process* for each of the accessing processes.
26
-
Out-of-process approach to IPC is simply incompatible with Chronicle Map's median latency target of < 1 μs.
28
+
Out-of-process approach to IPC is simply incompatible with Chronicle Map's median latency target of < 1 µs.
0 commit comments