Hi Pam,
> With regard to soft IOCs, at SNS, I built a "linuxStats" that was a few
> of the things from vxStats.
Would you mind emailing me the linuxStats module, or sending a link, so I can take a quick look? It's not in the soft support list.
> When I started thinking about the other
> things such as memory and CPU, it didn't seem to be relevant for a
> single soft IOC. (At SNS, we had many soft IOCs running in a
> server.)
If there's an easy, non-CPU-intensive way to get the %CPU used by the soft IOC process, that would be nice. Otherwise, it's best to let an external process monitoring CA client just write this information to soft PVs (though of course the PV name could be the same as the name for vxWorks/RTEMS CPU if to use the same display/ALH template...).
> I think Sheng did some work on the CPU statistics. I think those
> records ought to be per server, not per soft IOC, so they should be
> separate from the standard package for each soft IOC (which has boot
> time and heartbeats at SNS.)
I agree - all crate-centric or host-centric parameters should be in a separate app.
Thank you,
Stephanie
- References:
- devStats - OSI version of devVxStats Allison, Stephanie
- Re: devStats - OSI version of devVxStats Pam Gurd
- Navigate by Date:
- Prev:
Re: Base R3.14.10-RC1 Released J. Lewis Muir
- Next:
Re: devStats - OSI version of devVxStats Phillip Sorensen
- 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:
Re: devStats - OSI version of devVxStats Pam Gurd
- Next:
RE: devStats - OSI version of devVxStats Rees, NP (Nick)
- 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
|