• Decoding Output of spy command

    From VxWorksEnthusiast@21:1/5 to All on Thu Feb 23 11:12:08 2017
    Hi there, need help with decoding of Spy command. I have a system, where I have been trying to characterize some data, and whatever combinations that I try out, the spy output always shows tIdle is always lesser number.

    When I look at my other application task usage, most of the tasks are not using more than 5% of them, but am still seeing tIdle as less than 5

    I have couple of questions here.
    Why is the TOTAL always around 87% (I have never seen it around 100% or closer to it.
    I would have ideally liked my application to be around 20-25% of tIdle time. With the stats below, is my system in a bad-shape ?
    Can i assume that if the tSpyTask is not running, I have more CPU time under tIdle ?

    Please help me decode this and advise.

    Typical output is

    NAME ENTRY TID PRI total % (ticks) delta % (ticks)\ -------- -------- ----- --- --------------- ---------------\ tExcTask excTask 3c06788 0 0% ( 0) 0% ( 0)\ tLogTask logTask 3c089f8 0 0% ( 0) 0% ( 0)\ tShell shell 4eb3778 1 0% ( 2) 0% ( 0)\ tTnetShelld telnetd 4e0de38 2 0% ( 0) 0% ( 0)\ tRlogind rlogind fb390b8 2 0% ( 0) 0% ( 0)\ tSpyTask spyComTask 2b0ba130 5 13% ( 5392) 13% ( 188)\ tPoller f94b638 10 24% ( 9653) 24% ( 343)\ tAgent1 agt_1 fa27588 160 3% ( 1273) 2% ( 40)\ tAgent2 agt_2 fa81288 160 4% ( 1913) 4% ( 67)\ tAgtent3 agt_3 7669c28 180 2% ( 1155) 2% ( 33)\ txyTask xyTask() f93ec78 185 3% ( 1273) 2% ( 40)\
    tFM fmTask() f4e2728 190 1% ( 555) 10% ( 146)\
    tPM pmTask() fa57f78 190 1% ( 467) 1% ( 17)\ tHttpdTask 1386da28 190 5% ( 2146) 3% ( 53)\ tMyAgt2 2c71a410 190 6% ( 2771) 6% ( 94)\ tMyAgt3 2bdf00a0 190 3% ( 1250) 2% ( 34)\ tMyAgt4 2b0d16f0 190 4% ( 1682) 2% ( 33)\ tMyAgt7 2981e7f0 190 3% ( 1510) 3% ( 42)\ tMyAgt5 297fe3d0 190 4% ( 1972) 1% ( 23)\
    tIdle f94cf88 255 3% ( 1269) 0% ( 1)\ KERNEL 1% ( 504) 1% ( 16)\ INTERRUPT 7% ( 3147) 7% ( 97)\
    IDLE 0% ( 9) 0% ( 1)\
    TOTAL 87% ( 40017) 88% ( 1374)\

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From philippe.k.maisonneuve@gmail.com@21:1/5 to All on Fri Feb 24 02:08:24 2017
    Hi,

    This could be a sampling rate side effect. You may want to change the auxiliary clock rate before running spy.

    sysAuxClkRateSet (somePrimeNumber)

    Philippe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VxWorksEnthusiast@21:1/5 to philippe.k....@gmail.com on Mon Feb 27 08:28:44 2017
    On Friday, 24 February 2017 15:38:26 UTC+5:30, philippe.k....@gmail.com wrote:
    Hi,

    This could be a sampling rate side effect. You may want to change the auxiliary clock rate before running spy.

    sysAuxClkRateSet (somePrimeNumber)

    Philippe

    Thank you Philippe,
    The current rate on my system is configured as

    sysAuxClkRateGet
    value = 95 = 0x5f = '_'

    Are you suggesting it to increase this and verify it for more accurate % ?

    Regards

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From philippe.k.maisonneuve@gmail.com@21:1/5 to All on Tue Feb 28 00:20:13 2017
    It also depends on the system clock frequency.

    What you want is a frequency faster than the system clock and not a fundamental harmonic of it. Eg: When system clock is 100 Hz you can use 113 Hz for the auxiliary clock.

    Philippe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)