The db is in-memory. No disk writes when committing rows. I don't think I/O should be an issue.
Greg On Sep 18, 2:19 pm, Chuck Remes <[email protected]> wrote: > On Sep 18, 2009, at 12:11 PM, GregB wrote: > > > > > > > > > Chuck, > > > I thought the same thing so the code loads the data before starting > > the test run. Here are the steps: > > > Load 100,000 strings from a text file into a List<String>. Each > > String contains 55 columns of data. > > Start the timer > > Dispatch the strings to each "insert" threads Queue. Queue length is > > large enough that this will never block. > > The "insert" threads converts the string to an object - this does have > > some overhead but is stateless and should scale well. > > A PreparedStatement is used to insert into the table dedicated to the > > thread. > > When all "insert" threads are finished, stop the timer. > > Greg, > > I guess I wasn't clear enough. The steps outlined above certainly > reduce I/O for reading in the source data, but I'm more concerned with > the write I/O as you are committing rows to the table. Have you > saturated your disk when writing? > > cr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
