RE: Re: Archiver Appliance - Limit on PVs

[Sky Brewer via Tech-talk <tech-talk at aps.anl.gov>]

Hi Eusebio,

 

You shouldn’t have any performance problems with that setup for the Archiver Appliance, and you shouldn’t need more appliances unless you are in the 100 000 PV range (on a larger machine).

 

It’s very hard to debug performance problems, even harder from a distance. Some initial ideas

 

• How fast is the write interface to the var disk
• Is the STS on the var disk? Using RAM or the primary disk might help here.
• The JVM I believe takes whatever you give it, if you are running out of memory you should reduce what you gave it here. The sampleStartup.sh creates a tomcat per war file, so that’s 4x whatever memory you changed in the script. Since you have 8GB, probably 1GB is a safe number.

 

Deployments of the Archiver Appliance unfortunately is still quite site dependent and varied. Something I hope to improve by providing docker containers etc.

 

Some ideas:

There is a docker container version with all webapps in one instance https://github.com/archiver-appliance/epicsarchiverap/pkgs/container/epicsarchiverap/336979389?tag=singletomcat-61c7442

 

A variety of startup scripts in https://github.com/archiver-appliance/epicsarchiverap/tree/master/docs/docs/source/samples

 

Can’t remember if this is accessible outside of Sweden/Denmark, but ESS ansible deployment repository https://gitlab.esss.lu.se/ics-ansible-galaxy/ics-ans-role-epicsarchiverap (not updated for 2.05)

 

Hope that helps

 

Sky