It should be possible to initiate multiple asynch reads, and then wait
for them all to finish, instead of doing a read-one-wait-one loop.
On 2012-07-09 10:32, Steve McLeod wrote:
Hmm, I started looking at the async write approach, then realised that
the bottleneck is with reading, not writing. It's the "readFully" that
is the culprit. Any suggestions?
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
