Hi,
Sorry this isn't answering your question... but I've worked on a project
with thousands of threads and found it to not actually really cause any
issues (Except for hitting the thread limit for a process). Does the
large number of threads cause issues for you? I guess for large
scalability you could improve the number of open databases by 3 times,
but I would have thought at that scale you would hit memory issues?
You could also close idle databases dynamically (If over a threshold)?
And put a limit on the number of databases to open at a time? That
should help with memory usage too...
Just thinking, models for handling threads really interest me :).
Regards,
Ryan
On 13/02/2012 3:54 PM, Wolfgang Pedot wrote:
Hi,
I am using H2 in a scenario where there are lots of small/medium
databases in embedded-mode (multiple instances of the same design).
The code is designed to operate using thread-pools where possible in
order to keep the
thread-count in check but H2 log/lock-threads are making up ~2/3 of
the threads.
It would be great if there was a way for H2 to optionally use thread-
pools for log/lock-jobs to get those numbers down.
I have planned to check out the source-code myself but I dont know
when I will be able to make the time for that, any hints?
best regards
Wolfgang Pedot
--
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.
