From c18d16f3009c03e357f64651d910f19240e86d54 Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Tue, 23 Sep 2014 15:27:11 +0100 Subject: [PATCH] Update README.md --- README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d148d0aea..ea3a773db 100644 --- a/README.md +++ b/README.md @@ -65,9 +65,14 @@ If you compare HashMap, ConcurrentHashMap and Chronicle Map, most of the maps in Chronicle map lets you assign a map larger than your available memory, This will however impact performance as Chronicle Map will have to page the segments to and from disk as data is written or read from the map. This feature works brilliantly on Linux but unfortunately its not supported on Windows, if you use more memory than is physically available you will experience the following error : - - - +```java +Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) +j sun.misc.Unsafe.compareAndSwapLong(Ljava/lang/Object;JJJ)Z+0 +j net.openhft.lang.io.NativeBytes.compareAndSwapLong(JJJ)Z+13 +j net.openhft.lang.io.AbstractBytes.tryLockNanos8a(JJ)Z+12 +j net.openhft.lang.io.AbstractBytes.tryLockNanosLong(JJ)Z+41 +j net.openhft.collections.AbstractVanillaSharedHashMap$Segment.lock()V+12 +``` #### When to use ConcurrentHashMap Some of the time.