| Subject | Re: [Firebird-Architect] Can we, can we, can we????... |
|---|---|
| Author | Dmitry Yemanov |
| Post date | 2005-06-14T07:19:06Z |
"Dmitry Yemanov" <dimitr@...> wrote:
active grid with some not yet fetched rows will get a timeout error as soon
as he press the "down" key. Perhaps it's better to track the time spent in
the looper. This is neither a total request elapsed time nor a CPU time as
there're thread switches inside the looper. But this is the time elapsed in
the blocking mode (since the API call till its return), so I suppose this is
what people actually need.
Dmitry
>Well, a direct compare doesn't suit our needs perfectly. A user who has an
> > 2. How exactly are we going to track execution time of a request?
>
> Elapsed time. Every request has a timestamp of its beginning. Then we get
> the current time in the looper and compare.
active grid with some not yet fetched rows will get a timeout error as soon
as he press the "down" key. Perhaps it's better to track the time spent in
the looper. This is neither a total request elapsed time nor a CPU time as
there're thread switches inside the looper. But this is the time elapsed in
the blocking mode (since the API call till its return), so I suppose this is
what people actually need.
Dmitry