Re: [h2] autoCommitDelay and SET WRITE_DELAY

2015-07-13 Thread Thomas Mueller
Hi, Which version of H2 do you use? Just the wakeup every 50 milliseconds should not use 5% CPU. 50 ms is not high frequency; high frequency would be every millisecond or two. Could you get a few full thread dumps during the 5% CPU usage (jstack -l pid threadDumps.txt; about 10 times)? I guess

Re: [h2] mvstore for time series

2015-07-13 Thread Thomas Mueller
Hi, I think a regular (b tree) index is enough for your case. What queries do you use? In addition to the default MVMap (multi-version map), there is a map that supports concurrent write operations, and a multi-version R-tree map implementation for spatial operations. That's a documentation

[h2] mvstore for time series

2015-07-13 Thread alexrhelder
Hi, I was considering mvstore for time series data on a mobile device. - My usage would be high frequency writes (sensor data) and large batch reads of ranges. - The schema would be key=timestamp, value=data from multiple sensors What is unclear in my mind, is whether I should attempt

Re: [h2] Bug in array datatype handling?

2015-07-13 Thread christoff . schmitz
Unfortunately, H2 does not treat (1) as array. The same problem occurs when casting an integer to array: cast(1 as ARRAY) results in a single element array containing the String '1'. From: IanP i.pri...@surveybe.com To: h2-database@googlegroups.com Date: 2015-07-10 16:02 Subject: