h2.ModifyOnWrite and TestFileLockSerialized
29 views
Skip to first unread message
LRichard
Dec 13, 2011, 8:45:48 AM12/13/11
to h2-da...@googlegroups.com
Hello,
When I run the H2 unit tests TestFileLockSerialized with property h2.ModifyOnWrite set to true, the testTwoWriters test takes quite a lot of time (I killed it after about two hours). I'm wondering if there might not be an interlock. The main thread is hung on the "drop table test" statement whereas the other thread is on its "select * from test" statement.
I know the h2.ModifyOnWrite is new and not for production yet but maybe this information could help make it work better in most situations.
We made these tests because we're experiencing troubles with the SERIALIZED file_lock mode and are looking for improvements (see https://groups.google.com/d/topic/h2-database/unohFtz83cg/discussion for the troubles we're facing).
Regards
When I run the H2 unit tests TestFileLockSerialized with property h2.ModifyOnWrite set to true, the testTwoWriters test takes quite a lot of time (I killed it after about two hours). I'm wondering if there might not be an interlock. The main thread is hung on the "drop table test" statement whereas the other thread is on its "select * from test" statement.
I know the h2.ModifyOnWrite is new and not for production yet but maybe this information could help make it work better in most situations.
We made these tests because we're experiencing troubles with the SERIALIZED file_lock mode and are looking for improvements (see https://groups.google.com/d/topic/h2-database/unohFtz83cg/discussion for the troubles we're facing).
Regards
LRichard
Dec 15, 2011, 3:59:01 PM12/15/11
to h2-da...@googlegroups.com
The previous test was done on Windows 7 (on a recent workstation). The same test on MacOsX is faster : testTwoWriters is still much slower with h2.ModifyOnWrite set to true than with h2.ModifyOnWrite set to false but it ends after a few minutes (on a MacPro 2006 with MacOSX 10.6).
Reply all
Reply to author
Forward
0 new messages