Re: How I dramatically sped up DB file updating

Bob Richardson wrote:
>
> varied from 30.5 to 29.5, just rerunning the exact same program. I've
> attributed this to the fact that there's always "stuff" going on in the
> background of Windows - which affects the overall time.
> How do you get consistent, accurate times?

And if you got those accurately repeating times out of Windows'
hick-uping process hassle, what exactly would you do with those numbers?
I mean what to do with them within your DB app tuning and development
work?

I myself have never been able to write so sophisticated application that
it first had been a slow sluggish dog. And after tuning the response
times down by 3,3% (30.5 sec --> 29.5 sec) it had turned to a good and
usable application:)

I know I myself having a tendency to start examining some oddities, that
are often more interesting than the current, anesthetic, daily DB app
writing.
But this time I'll make a promise that I absolutely will not do anything
to even try to think, nor run any tests to get some usable answer to
what would originally achieve, and what final tricks would get away
those 1 second test fluctuation you have discovered:)

Well if you do, and if you find a credible answer, don't hesitate to
post it here. The answer may be interesting to know anyway.<g>
DB1
.