Hi, As I wrote, opening many databases concurrently is problematic anyway:
- out-of-memory problems when using the default cache settings - bad or cache hit rate / very bad cache efficiency - "too many open files" problem Therefore I consider using a thread pool as trying to solve the wrong problem. As Christoph wrote "every feature is a potential place for bugs" and as Noel wrote "we don't like adding complexity unless it makes a measurable difference." - to me this would include having a measurable difference to opening _fewer_ databases. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-database@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
