Accurate LotusScript timing technique

Have you ever wanted to do timing tests on your LotusScript code but found that NotesDateTime variables don't measure a small enough time interval? With NotesDateTime, you can only time to 100ths of a second. It's possible to get more accuracy by making system-dependant calls, but that ties the timing code to a particular OS. That could be a problem for you if your server is Unix, Linux, or AIX-based and your clients are all Wintel systems. Wouldn't it be nice if there was a system-independent way to time your code more accurately? Well, now there is.

Download this free guide

Download: IT Certifications 101

Inside this exclusive essential guide, our independent experts break down which IT certifications are worth your time and effort, and how to get started obtaining them to further your career— including specific certifications that any cloud or desktop pro should seriously consider.

Start Download

• Corporate E-mail Address:

  You forgot to provide an Email Address.

  This email address doesn’t appear to be valid.

  This email address is already registered. Please login.

  You have exceeded the maximum character limit.

  Please provide a Corporate E-mail Address.

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent.

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

There's a LotusScript function called GetThreadInfo that can get a variety of useful information for you. There's a trick to using this function, though. The key insight that made this code work is that I used numbers rather than the literal definitions (LSI_THREAD_TICKS etc.) listed in the help file. For some reason, if you use the literals, the code compiles, but fails when it runs (true for both R5 and ND6).

Here's the code:
**********************************************************
stc = Getthreadinfo(6) ' get the starting tick count

<the code you want to time>

ftc = Getthreadinfo(6) 'get the final tick count
tps = Getthreadinfo(7) 'get the ticks per second

t = (ftc - stc) / tps  'final tick count minus starting tick 
count divided by ticks per second yields duration.
**********************************************************

Here's a list of the OSes and Notes versions that this tip has been tested with. I'd like to thank Andrew Pollack of Northern Collaborative Technologies and Penumbra Group for their assistance with this testing. Note that AIX and Solaris systems will permit much finer measurements. One thousand ticks per second has been enough for all the testing I've done so far.

• Win2000 Domino 6.0 (ticks per second 1000)
• Win2000 Domino 5.0.9a (ticks per second 1000)
• AIX 4.3.3 ML 9 with Domino 5.0.11 (ticks per second = 1,000,000)
• Solaris 8 with Domino 5.0.11 (ticks per second = 1,000,000)
• SuSE Linux 8.1 with Domino 6.0.1 (ticks per second 1000)
• Server.Version.Notes = Release 6.0.1; Server.Version.OS = SunOS 5.8 Generic_108528-18 (ticks per second 1000)

stc = Getthreadinfo(6) 'get the 
starting tick count

<the code you want to time>

ftc = Getthreadinfo(6) 'get the final tick count
tps = Getthreadinfo(7) 'get the ticks per second

t = (ftc - stc) / tps  'final tick count minus starting 
tick count divided by ticks per second yields time.