Andy Foster (Royal Greenwich Observator)
reported that devVXStats reports cpu usage
incorrectly. I ran a test case and agree
with Andy.
It is using sysClkRateGet in a place where
it should use the spy sample rate.
By default it uses a spy sample
rate of 80 Hz . Thus if the vxWorks clock
is 60Hz it overstates cpu usage by 80/60 = 1.333.
In looking at code it is also reporting file descriptor usage
not tcp connections.
This code needs to be looked at carefully before the next
base release.
Marty Kraimer
- Navigate by Date:
- Prev:
Re: VxWorksp2 is ready now! Bakul Banerjee
- Next:
edd/dm fonts Rolf Keitel
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Getting macro substituted channel names in sequences Ron Chestnut
- Next:
edd/dm fonts Rolf Keitel
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|