| 3 Votes |
Evaluation Loop Average
Relevance
| * Results in a "string"/number |
less significance 3 of (average of evaluationcycle of client as floating point / 1000 / 60)
Property Details
| 2166 | |
| Evaluation Loop Average | |
| Client Evaluation Loop | |
| Average Client Loop (evaluation cycle) in minutes | |
| danielheth | |
| danielheth on 1/29/2013 10:06:15 PM | |
| 20 Downloads | |
* Average over 0 ratings.
** Log In or Register to add your rating.
|
Sharing
Relevance Image Sharing:
|
| Social Media: |
Comments
 |
|
| Yup, jugs tee has it right. This one gives u more accurate info with the additional decimal values. This one was /is a better version of that older statement. Relevance statements don't get version'ed like fixlets and analyses. The previous statement is still functional, just this one is better. Both show examples of writing relevance which is why I leave both up on the site. | |
 |
|
| Expand the "Example Results" of both to see what I mean. | |
|
|
| I believe this one will result in decimal values, and the other will be an integer. | |
 |
|
| What is the difference between this one and: http://bigfix.me/cdb/Relevance/1056? | |
|
|
| This seems like a good thing to add to an analysis to gauge the "health" of the TEM clients and their ability to report in reasonably. | |
|
|
| So this is related/similar to: http://bigfix.me/cdb/Relevance/1056 | |
|
|
| Yes. In some very large organizations with alot of content, actions, console operators and such... their client loop plays a major factor when trying to design new projects. Some projects involve automatic shutdown/startup using vPro or other technologies, and timing is very important. To help with that, we could use this relevance to determine how long the endpoint is taking to go through it's entire client loop (evaluating actions, content, global properties, site subscriptions, etc...) | |
|
|
| So what does this represent? How often it takes a client to work through all of its relevance evals? | |
