Difference between normal read and condition variable reads

[GoogleCodeExporter]

Atm a transaction uses all read handles to listen to when it needs to
retry. A lot of values these handles refer to are immutable (see the queue
and both the stacks it uses, these stacks are final) so there is no need to
listen to change on handles that will never change.

This should reduce the overhead for condition variables because there is
less administration going on.

Original issue reported on code.google.com by alarmnum...@gmail.com on 5 Feb 2009 at 9:51

[GoogleCodeExporter]

The MultiversionedStm now has special support for immutable datastructures. 
Immutable
stm objects will not be tracked in the session and will not be hydrated. Only
hydrated handles are used for condition variables. So there is no reason to 
make a
distinction between normal reads and condition variable reads.

Original comment by alarmnum...@gmail.com on 8 Feb 2009 at 11:27

• Changed state: Fixed