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

rewored to - If after some business logic, in our example after reading the 'issueDate' and

Browse Source 
'symbol', you wish to remove the entry, its more efficient to use the 'context' directly to remove the entry. The
             'context' is already aware of the entries location in memory. So it will be quicker to call
             `context.removeEntry()` rather than `map.remove(key)`.
This commit is contained in:
Rob Austin
2014-12-21 09:39:59 +00:00
parent 6d1a13745f
commit 4eb461392e
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -5
View File
@@ -579,8 +579,8 @@ look-ups and making your code run slightly faster.
#### acquireUsingLocked()
If you are only accessing ChronicleMap from a single thread. If you are not doing replication
and don't care about atomic reads. Then its simpler ( and faster ) to use acquireUsing() otherwise we
recommend you use `acquireUsingLocked(key,value)` as this gives you atomicity.
and don't care about atomic reads. Then its simpler ( and faster ) to use `acquireUsing(key,
value)` otherwise werecommend you use `acquireUsingLocked(key,value)` as this gives you atomicity.
The acquireUsingLocked(key,value) method holds a segment write lock, as it will update or put a
new entry into the map, this is unlike getUsing
@@ -600,9 +600,11 @@ try (WriteContext<?, BondVOInterface> context = map.acquireUsingLocked("one", bo
}
```
If after you have read the 'issueDate' and 'symbol' and you wish to remove the entry based on some
business logic, its more efficient to use the 'context' to remove the entry, as the contents is
already aware when the entry is in memory.
If after some business logic, in our example after reading the 'issueDate' and
'symbol', you wish to remove the entry, its more efficient to use the 'context' directly to remove the entry. The
'context' is already aware of the entries location in memory. So it will be quicker to call
`context.removeEntry()` rather than `map.remove(key)`.
## Oversized Entries Support