Hi Ken,
I changed caEventRate so that it has a 1:1 ratio for channels to
monitors in order to better reflect reality. I committed this version to
CVS. This caused the server's CPU to saturate. This also caused the
maximum event rate from the gateway to drop down to 250k events per sec.
Connecting to CA Channel "joh:jane" 40000 times. done. Subscribing 40000
times. done. Waiting for initial value events. done. CA Event Rate (Hz):
current 194227 mean 194227 std dev 0.00101583 CA Event Rate (Hz):
current 239705 mean 216966 std dev 22738.8 CA Event Rate (Hz): current
256943 mean 230292 std dev 26454.6 CA Event Rate (Hz): current 254222
mean 236275 std dev 25144.8 CA Event Rate (Hz): current 253042 mean
239628 std dev 23469 CA Event Rate (Hz): current 253130 mean 241878 std
dev 22007.1 CA Event Rate (Hz): current 253139 mean 243487 std dev
20752.2 CA Event Rate (Hz): current 252582 mean 244624 std dev 19643.5
This seems to indicate that the locking overhead is significant.
Jeff
__________________________________________________________
Jeff Hill Internet [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
- Navigate by Date:
- Prev:
R3.14 portable ca server monitor throughput performance has been improved Jeff Hill
- Next:
RE: MEDM 3.13 vs. 3.14 Jeff Hill
- Index:
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
R3.14 portable ca server monitor throughput performance has been improved Jeff Hill
- Next:
RE: MEDM 3.13 vs. 3.14 Jeff Hill
- Index:
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
|