Also, if I set MVCC=TRUE instead, the behavior is the same except the lock
is in Command.executeQuery.
On Saturday, December 10, 2016 at 1:17:39 PM UTC-8, Brian Craft wrote:
>
> Using an older version, 1.3.175, PageStore engine, with
> MULTI_THREADED=TRUE, when multiple threads are running read
multi_threaded was very very experimental back then.
it's getting better now, and with current master I'm running it myself
(with the MVStore) engine in my QA to flush out issues.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe
How can I select pageStore in 1.4? I haven't found the option in the docs.
If I've written the file with 1.3, perhaps 1.4 will find an engine setting
in the db?
So I understand, is getPage() fetching from disk? Using a profiler,
getPage() is the top hot-spot. I'm not sure why the profiles don't
Not getting far with 1.4. I realized I could use PageStore by setting
MVCC=FALSE, but the performance is pathologically slow, for me. My test,
which takes 28 seconds in 1.3, has run for 20 minutes without completing,
with 1.4.
I rebuilt the database table, to be sure it wasn't a 1.3 vs. 1.4 da
(a) you need to use MV_STORE=FALSE to select PageStore in 1.4
(b) we have not done any work on making MULTI_THREADED work better with
PageStore, nor do we intend to.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group
