Thanks for the info, anything is better than nothing. Any chance to measure something like 1000 records per commit. With one record per commit for the update operations you are not really measuring the work to do the operation just the overhead of commit -- at least for the single user case -- assuming your machine is set up to let derby do real disk syncs (no write cache enabled).
Knut Anders Hatlen wrote: > Mike Matrigali <[EMAIL PROTECTED]> writes: > > >>Olav Sandstaa wrote: >> >> >>>Kathey Marsden <[EMAIL PROTECTED]> wrote: >>> >>> >>>>Right now we fly without a net for performance. Does anyone run any >>>>regular performance regression tests, especially ones for which they >>>>might be able to post results? >>> >>> >>>The results from the performance regression test I run are now >>>available on the following Web page: >>> >>> http://home.online.no/~olmsan/derby/perf/ > > >>How often are commits executed the single record operation tests? > > > One record per transaction. Autocommit is off. >
