Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Units used in SMQUERY.SMELAPTIME

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Units used in SMQUERY.SMELAPTIME
 Login/Join
 
BG
Member
posted
I'm evaluating report usage via Resource Management. I've been looking at the SMQUERY and I'd like to pull out the elapsed time for report execution. I've seen some references that indicate this value is in seconds. I've also seen a reference that indicated is was in 10000th of a second. Neither actually works out. I had a long running report that completed in 9-10 minutes based on me staring at a timer. For that report, the SMELAPTIME value is 9220.

Does anyone know for sure what's stored?

This message has been edited. Last edited by: Kerry,


WF 7.7.03
Windows Server 2008
Just about all Output types
 
Posts: 10 | Registered: September 12, 2008Report This Post
GinnyJakes
Expert
posted Hide Post
According to the documentation:
quote:
SMELAPTIME Integer The amount of elapsed time used by the
request in 10000th of a second.

I got this out of the i_rg.pdf manual, Appendix B. If you can find the base masters, they also contain lots of defines.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
BG
Member
posted Hide Post
I found the same documentation but it looks fishy to me.

If I'm doing the math right and the SMELAPTIME for this report is 9220, that would mean the report ran for 92200000 seconds or, approximately, 25000 hours. I'm certain I did not wait that long.

Assuming I had that wrong and I need to work the other direction (divide by 10k instead of multiply) that would mean it ran for .922 seconds. That's closer but doesn't explain the other 9 minutes it took for the report to display.

Am I missing something?


WF 7.7.03
Windows Server 2008
Just about all Output types
 
Posts: 10 | Registered: September 12, 2008Report This Post
j.gross
Virtuoso
posted Hide Post
9220 x (1/10000) = 0.9220
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
BG
Member
posted Hide Post
Thanks for the response. The .922 second comment confirms the second paragraph of my previous post.

I'm still unsure as to what that number actually represents. What exactly is it tracking?

For example, I just ran a Focus Executable from DevStudio. The results came back in 12 seconds. It's based on a SQL Stored Procedure which, when I ran it with the same parameters prior to running the report, it came back in 4 seconds. I'm assuming the non-sproc work amounts to the other 8 seconds. For that execution, SMELAPTIME was 9830 or, based on the above calculation, is .983 seconds. Those numbers don't work together.


WF 7.7.03
Windows Server 2008
Just about all Output types
 
Posts: 10 | Registered: September 12, 2008Report This Post
CT
Gold member
posted Hide Post
You can include the following before and after the code you are monitoring in your fex.
 
-SET &TIMECHEK = HHMMSS(TIMECHEK);
-TYPE &TIMECHEK


7.6.9, XP
 
Posts: 60 | Location: Cary, NC | Registered: February 19, 2008Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Units used in SMQUERY.SMELAPTIME

Copyright © 1996-2020 Information Builders