instead of maintaining background threads to do writing and such as you are doing now, you could just spawn tasks that do it. Why tie up an expensive resource like a thread just to perform an intermittent task? Let the system maintain a thread pool based on the load on the system. If you are using H2 as an in-memory, in-process db, the task-based approach will use threads more efficiently.
On Dec 10, 2010, at 3:48 PM, Matt Bishop wrote: > > Is there some place in particular that you think something therein > would be helpful? > > > On Dec 9, 8:04 am, Rami <[email protected]> wrote: >> Hi, >> >> I just noticed that h2 does not utilize java.util.concurrent (and 2 >> related) packages. >> Is this a planned thing or just baggage from the past? >> >> - rami > > -- > 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. > -- 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.
