Re: archiving system

[Ralph Lange <Ralph.Lange@bessy.de>]

 Dirk,

James Rowland from Diamond recently did a poll and has the most current 
list of archiving solutions that are used with EPICS. I think he will 
talk about it at the upcoming EPICS Collaboration Meeting in two weeks.

My first order answer would be:

There's the Channel Archiver: old, stable, fast, very widely used, but 
not based on a RDB.
There are several other archiving solutions, some of which use a RDB for 
storage, others don't. Different ages, different languages, different 
file formats or RDB systems for storage. Their common feature: they are 
all used at one lab only, two labs maximum.
CSS databrowser support is available for the Channel Archiver, and for 
the Oracle-based archiver at SNS. (The latter might not be part of the 
DESY CSS.) There is experimental support for HyperArchiver (Channel 
Archiver writing into Hypertable).

While RDB-based archiving solutions have a tendency to be slower (as 
well in writing an archive as retrieving from it), I don't see an issue 
here for your system (unless your 10K channels are updating every second 
or faster).

Hope this helps,
Ralph


On 28.09.2010 10:23, Dirk Martin wrote:
> Hallo,
>
> at the S-DANILAC of the TU Darmstadt we're using EPICS to control power
> supplies for example. Since it is necessary to observe ~10000 PVs for a
> period of nearly four weeks, we decided to introduce an archiving system
> based upon a relational database. We're using CSS (from the DESY) and
> would like to plot the archived data in the Data Browser.
>
> That is why I ask you, whether you could tell me, which archiving system
> is wide-spreaded enough and best for this job.
>
>
> Thanks in advance and best regards
>
> Dirk Martin