Millisecond-resolution clock

[Łukasz997 128]

Good morning,

is there a millisecond-resolution wall clock available in HC3 QuickApps?

As I want to measure between-quickapp communication latency, the os.clock() is not a solution - I checked and it measures just CPU time.

Or - is there a method to measure a single quickapp millisecond run time, not only CPU time of the application?

Edited 5 hours ago by Łukasz997

[jgab 2,656]

Make a 100 or 1000 request with os.time and calculate the average round trip...

 

Edited 2 hours ago by jgab

[m.roszak 780]

Yep, this is only solution.

Lua does not support natively ms.

[Łukasz997 128]

Thank you very much. In my particular case this will not help - measurig points incomes "at it's will", instead of one-after-one stream.

I heard about socket.gettime but not here...

 

Basically, the need for this arose because, for a new idea of mine, I wanted to check how reliable a hub.call to another QuickApp actually is. 

 

By the way, I am attaching these two little programs, the sender and the receiver. This may be an interesting experiment for some of you, showing just how much is happening inside that black box.

Before start, you need to enter the correct IDs of both programs in the sender (SENDER and RECEIVER constants), so that it can filter out the communication between them. 

The sender sends a call to the receiver together with its own counter value. The receiver receives it, but also maintains its own counter, which must match the value it received. In addition, the average number of events per hour is calculated over a twelve-hour rolling window. Once the window has been filled, the minimum and maximum events-per-hour values will also be updated.

Number of missing hub.calls will also be shown.

 

I also wanted to measure the sender-receiver-sender round-trip time “in real life”, but unfortunately, that cannot be done...

Please login or register to see this attachment.

Please login or register to see this attachment.