When creating a new key, it is essential to check that it is not already present in memcached.
When a memcached key does not directly refer to a system element but – for example – to derived quantities, the format of its name is free and can be arbitrary defined, provided that it is not already used.
Even though the name format is arbitrary, it is advisable to always use UPPERCASE and append an extension separated by a "_" (e.g. MY-ARBITRARY-NAME_DAT). In any case, do not use the "_AUX" extension for a "free key".
To avoid the proliferation of extensions, try using the ones listed in the table below:
| Extension | Description |
|---|---|
| _BUF, _JBUF* | Data buffers (FIFOs , circular buffers, etc...), not necessarily associated with a system element. |
| _INFO, _JINFO* | Static metadata, not necessarily associated with a system element. |
| _DAT, _JDAT* | Generic data structures, not necessarily associated with a system element. |
(*) "J" prefix indicates that the key content is a Json document.
- Beam sigmas
- BTF DAQ
- DAFNE INFERRED STATE & CURRENT LIFE TIMEs
- DAFNE state
- DCT (Current monitor)
- DHPTB102_AUX
- FLAME state
- GOD, ORB (Orbit)
- Kickers shot delay
- Linac Status