Recent changes to 15: CuckooStripedSet - huge memory consumption

#15 CuckooStripedSet - huge memory consumption

khizmax — Thu, 12 Dec 2013 18:20:13 -0000

summary: CuckooStripedSet - huge memory consumtion --> CuckooStripedSet - huge memory consumption
Description has changed:

Diff:

--- old
+++ new
@@ -1,2 +1,2 @@
-Huge memory consumtion is observed when many threads (more than 4) perform insertion. In such case several threads can make rehashing i.e. make deep copy. 
+Huge memory consumption is observed when many threads (more than 4) perform insertion. In such case several threads can make rehashing i.e. make deep copy. 
 Possible solution: introduce a new flag "rehashing in progress". Only one thread can set this flag, any others must spin on it if it is set.

CuckooStripedSet - huge memory consumption

khizmax — Thu, 12 Dec 2013 18:07:43 -0000

Ticket 15 has been modified: CuckooStripedSet - huge memory consumption
Edited By: khizmax (khizmax)
Summary updated: u'CuckooStripedSet - huge memory consumtion' => u'CuckooStripedSet - huge memory consumption'
Description updated:
--- description-old

+++ description-new

@@ -1,2 +1,2 @@

-Huge memory consumtion is observed when many threads (more than 4) perform insertion. In such case several threads can make rehashing i.e. make deep copy.
+Huge memory consumption is observed when many threads (more than 4) perform insertion. In such case several threads can make rehashing i.e. make deep copy.
Possible solution: introduce a new flag "rehashing in progress". Only one thread can set this flag, any others must spin on it if it is set.

CuckooStripedSet - huge memory consumtion

khizmax — Thu, 12 Dec 2013 18:07:43 -0000

Huge memory consumtion is observed when many threads (more than 4) perform insertion. In such case several threads can make rehashing i.e. make deep copy.
Possible solution: introduce a new flag "rehashing in progress". Only one thread can set this flag, any others must spin on it if it is set.