Nested top action performance regression

Zhoutall / stasis

Automatically exported from code.google.com/p/stasis

Other

0 stars 0 forks source link

Nested top action performance regression #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

r1179 introduced a performance regression.

In order to write a CLR, we copy the compensated entry into the new entry.
 This causes the log to seek backwards, and perform a read.  The log has
not been optimized for this case, and performs a synchronous write in order
to obtain the older entry.

Original issue reported on code.google.com by sears.ru...@gmail.com on 13 May 2009 at 1:54

GoogleCodeExporter commented 9 years ago

Original comment by sears.ru...@gmail.com on 13 May 2009 at 2:02

Added labels: Priority-Critical
Removed labels: Priority-High

GoogleCodeExporter commented 9 years ago

Fixed in r1192.   Haven't performed careful performance comparison with a 
pre-r1179
stasis.

Original comment by sears.ru...@gmail.com on 14 May 2009 at 9:29

Changed state: Fixed