Genome

[Masafumi Kashiwagi]

Hi everyone,

When I execute genome benchmark in Deuce STM with TL2 it never
finishes.
I want to know if it's normal or I am doing something wrong.
If I use SLA there is no problem.

The execution command is as follows.
java -
Dorg.deuce.transaction.contextClass=org.deuce.transaction.tl2.Context -
javaagent:bin/deuceAgent.jar jstamp.genome.Genome -g 256 -s 64 -n
16384 -t 4

Thanks.

[Guy Korland]

Can you retrieve the latest version from the SVN?

We fixed a major bug in our TL2 but it's not included yet in the public build.

--
You received this message because you are subscribed to the Google Groups "Deuce-STM" group.
To post to this group, send email to deuc...@googlegroups.com.
To unsubscribe from this group, send email to deuce-stm+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/deuce-stm?hl=en.

[Masafumi Kashiwagi]

Hi Guy,

Thanks for your reply.
I'm already using the latest version from the SVN(rev457).
It seems like a transaction never commits when a read-after-write occurs.
In TL2 ReadSet.checkClock, the method checks for the clock and the
lock of each read set,
but it does not check who is locking the field.
So when the field is locked by its own transaction, checkClock always fail.

2011/11/4 Guy Korland <gkor...@gmail.com>:

[Guy Korland]

Thanks it seems like you're right, I was sure I fixed it long ago but it seems like the bug is still there.

I'll try to commit a fix soon.

Thanks,

Guy