On Wed, Apr 4, 2012 at 4:23 PM, esbreidenbach <scottb@...>wrote:

>
> The stored procedure is run as part of a desktop application. The purpose
> of the procedure is to update two integer fields in a table. The values for
> these fields are updated based on a number of other factors which I wont
> bother you with, but suffice it to say that they change often. Whenever
> the procedure is run, it would update approximately the same number of
> records; the time of day does not affect the amount of "work" it has to do.
>
> The user runs the procedure often during the day. A connection to the
> database is made when the user first logs in, so I am assuming that the
> initial delay is not due to making a connection.
>

OK, have your customer get the database header information at four times
during the day. The way I'd do it is with gstat -h. Run it first thing -
before the work day starts, again at 11 AM, again at 3 PM and again at the
end of day.

My guess is that the zombie processes are keeping a transaction active all
day, then being cleaned up overnight, leaving lots of garbage collection
for the first guy in the morning.

Good luck,

Ann


[Non-text portions of this message have been removed]