Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018 
<== Date ==> <== Thread ==>

Subject: Re: autosave limitation?
From: Tim Mooney <mooney@aps.anl.gov>
To: Tim Mooney <mooney@aps.anl.gov>
Cc: Emmanuel Mayssat <emayssat@outlook.com>, emmanuel mayssat <emmanuel_mayssat@lynceantech.com>, tech-talk@aps.anl.gov
Date: Fri, 12 Apr 2013 09:51:57 -0500 (CDT)
Whoops, sorry I was wrong.
Autosave has a #define'd limit of eight restore-file names.  This can easily be increased, or the list
of restore-file names could be implemented with a linked list.
Tim


From: "Tim Mooney" <mooney@aps.anl.gov>
To: "Emmanuel Mayssat" <emayssat@outlook.com>
Cc: "emmanuel mayssat" <emmanuel_mayssat@lynceantech.com>, tech-talk@aps.anl.gov
Sent: Friday, April 12, 2013 9:39:01 AM
Subject: Re: autosave limitation?

Hi Emmanuel,

Autosave doesn't have a coded limit on the number of files it's handling.  Bob Dalesio's original code
used a linked list, and that's how it still works.  I haven't tested large numbers of files, but in some ways
splitting an autosave file into several smaller ones would improve the overall efficiency by decreasing
the number of unchanged PVs that are written when one PV changes.

Autosave has only eight sets of status PVs, but the only consequence of going over that limit is that
a file's status will not be available via PVs.

You can run only a single instance of autosave in an IOC, because two instances would run into
name conflicts.

There is another possibility:  If you make a single autosave request file from many individual files, using
the include-file mechanism, you have most of what is needed to later split off an application to a different
IOC.  You could copy the full save file to the new IOC and just put up with the error messages the first
time autosave tries to restore PVs that don't exist in the IOC.  Boot-time restore is strictly limited to the
ioc in which it runs.  (However, manual restore does not limit itself to the ioc in which it runs.)

Tim


From: "Emmanuel Mayssat" <emayssat@outlook.com>
To: tech-talk@aps.anl.gov, "emmanuel mayssat" <emmanuel_mayssat@lynceantech.com>
Sent: Thursday, April 11, 2013 6:43:32 PM
Subject: autosave limitation?

I have several device running in a master IOC.
I would like to use autosave.

The issues is that I would like to break down my master IOC into smaller ones at will (for development purpose).
I would like to use several req files and restore files for autosave.
In other words, I would like to have one autosave configuration per device in the master IOC.

Q: Is there a limitation to the number of files and instance of autosave in a single IOC?



Regards,
--
Emmauel



References:
Re: autosave limitation? Tim Mooney

Navigate by Date:
Prev: Re: autosave limitation? Tim Mooney
Next: Re: CSS BOY - global widget properties modification Kasemir, Kay
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018 
Navigate by Thread:
Prev: Re: autosave limitation? Tim Mooney
Next: CSS BOY - global widget properties modification Vítek Michal
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·