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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Questions about Name Resolution Server |
From: | "Johnson, Andrew N." <[email protected]> |
To: | renato sanhueza <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Sat, 23 Dec 2017 05:15:53 +0000 |
Hi Renato,
The Channel Access network protocol which has been exclusively used by EPICS until fairly recently relies mostly on UDP broadcasts for name resolution within a single subnet. Whether that is scalable depends on your needs — at the APS we have well over
400 IOCs (I forget the actual number and I’m not at work to be able to look it up right now) on a single subnet, and we don’t have problems related to useless packets. Channel Access does use carefully developed algorithms for name searches which try to minimize
the number of search packets. We did have problems here with packet storms when bringing the whole machine up after an incident such as a site power failure about 17 years ago, but adjustments were made to the search algorithms at the time and those issues
have not recurred since.
For sites that are large enough to need multiple subnets we generally recommended the installation of gateway processes to bridge the different subnets, and a name-server can be used as well
(or possibly instead) to further reduce broadcast traffic, but that does generally require the name-server to be informed where every PV is located.
The new pvAccess protocol is still comparatively new and we haven’t prioritized the development of alternative name resolution methods yet; other features have been higher on our list to date, but certainly the ability to do name resolution over TCP is
something that we would like to add. Our development team is fairly small though, and we are always open to ideas and contributions from other developers.
HTH,
- Andrew
--
Sent from my iPad
|