in reply to Re: Design thoughts: iterator invalidation
in thread Design thoughts: iterator invalidation

RCU is optimized for the read case and so writes can be very slow.

Writes can't be very slow. Garbage collection of prior copies can be significantly delayed.

The closest thing to writes being slow is that you have to create an entire new unit so having huge units leads to having to copy the full unit in order to make an update. If that makes your writes slow, then you probably need to split that huge unit up.

- tye        

  • Comment on Re^2: Design thoughts: iterator invalidation (RCU)

Replies are listed 'Best First'.
Re^3: Design thoughts: iterator invalidation (RCU)
by RichardK (Parson) on Feb 20, 2015 at 18:13 UTC

    True, but as there can only be one active writer, if there are many threads trying to write to the list you have to wait your turn to get the write_lock. Once you've got the lock _then_ it's fast.