2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: CA gateway chaining |
From: | "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov> |
To: | Dirk Zimoch <dirk.zimoch at psi.ch> |
Cc: | EPICS core-talk <core-talk at aps.anl.gov> |
Date: | Mon, 25 Oct 2021 16:32:03 +0000 |
On Oct 25, 2021, at 3:53 AM, Zimoch Dirk (PSI) via Core-talk <core-talk at aps.anl.gov> wrote:
I’m not sure that arrays really get higher priority anywhere, but once the CA server has started to put an array value onto the wire it can’t be interrupted with updates from any other channels until every TCP packet holding that array data has
been sent out. I believe (but I might be wrong) the CA gateway has a single-threaded server side, so sending a single large array through it will hold up every other channel that wants to pass through the gateway at the same time even if the two end-points
are completely unrelated to the array channel.
IIRC the PVA protocol and gateway were designed to be a lot more efficient at handling large amounts of array data, which is why I would recommend using PVA for areaDetector transport.
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|