Re: ? Forms load test, keystroke files, 2nd commit LONG ?

bamon_at_ocvaxc.cc.oberlin.edu writes in article <bamon-210194082907_at_amon.cc.oberlin.edu>:
>
> The first time we query up a master/detail set and make a change, the
> commit takes about 1-3 seconds, and the second time we query the same
> m/d set and make a change, the commit takes between 30-120 seconds,
> with most commits falling into the 30-50 second range.
>
> I'm wondering if the second change is forcing the first change to
> be written to the database from the buffers? I'm really at a loss
> here. Ideas?
>

There may be a lot of reasons that the commit-time is increasing, but to me it sounds like a locking-problem.

You should turn on SQL_TRACE and compare the trace-files of a "fast" and a "slow" update. It should be easy to see if the database actually does more work on the "slow"-updates, or if it is simply waiting for freeing some resources.

Willy

Willys Mail     FidoNet   2:2407/907  2:2407/908     Mail Only System
                CIS: 100020,3517       USR Courier HST dual standard
                willyk_at_kbigate.stgt.sub.org
                ->   No Request from 06.00 to 08.00 <-
======================================================================