Easy to Create, Easy to Change - Easy to use!


GetCurrent("ScientificTime") added to GetCurrent() to give better precision for timers (Ver. 8.5.0.2500)

Started by DataEase
You will need to Sign In to be able to comment on the Blog!

GetCurrent("ScientificTime") added to GetCurrent() to give better precision for timers (Ver. 8.5.0.2500)

Download Sample

When DataEase was introduced back in the early 1980ies computers where so slow that seconds was more than precise enough for timing things.

However this is no longer the case and haven't been for some time. It was a big problem for us when we timed speed of processes in DE85 as they would invariably take less than a second but the information we got was either 0 or 1 (fitting in many ways, but not very informative).

it would take 1 seconds if we started the test just before the second changed, and 0 if it managed to finish in less than a second when it started early in a second count.

For scientific purposes it was useless!

We would maybe let this dog lay if that was the far this problem reached but we are now working with advanced locking/data consistency issues and then it is not very useful when all the records etc. has the exact same time stamp.

When working with processing the new 1/1000 might not even be sufficient but it is a massive improvement over the early function so we will give it a try.

You might not need this function right now but it will be quite useful when you are testing your procedures etc as you can see the difference in performance inside a second rather than having to run the procedure for longer to see if there is any effect to your efforts.


Written by DataEase 08/09/16 at 11:07:37 Dataease [{8}]FIVE