577c73af0e
* New translations volumio.properties (French) * New translations astro.properties (Finnish) * New translations chromecast.properties (Finnish) * New translations icloud.properties (Finnish) * New translations tradfri.properties (Finnish) * New translations icalendar.properties (Finnish) * New translations dali.properties (Finnish) * New translations fmiweather.properties (Finnish) * New translations modbus.properties (Finnish) * New translations mybmw.properties (Finnish) * New translations netatmo.properties (Finnish) * New translations rollershutter.properties (Finnish) * New translations vat.properties (Finnish) * New translations avmfritz.properties (Italian) * New translations enigma2.properties (Italian) * New translations astro.properties (Dutch) * New translations openweathermap.properties (Dutch) * New translations dsmr.properties (Dutch) * New translations systeminfo.properties (Dutch) * New translations unifi.properties (Dutch) * New translations jsscripting.properties (Dutch) * New translations inmemory.properties (Dutch) * New translations mapdb.properties (Dutch) * New translations rrd4j.properties (Dutch) * New translations smhi.properties (Swedish) * New translations plex.properties (Italian) * New translations openwebnet.properties (Italian) * New translations solarforecast.properties (Finnish) * New translations nikohomecontrol.properties (Dutch) * New translations emotiva.properties (Italian) * New translations volumio.properties (Italian) * New translations siemenshvac.properties (Italian) |
||
|---|---|---|
| .. | ||
| src | ||
| NOTICE | ||
| pom.xml | ||
| README.md | ||
InMemory Persistence
The InMemory persistence service provides a volatile storage, i.e. it is cleared on shutdown.
Because of that the restoreOnStartup strategy is not supported for this service.
The main use-case is to store data that is needed during runtime, e.g. temporary storage of forecast data that is retrieved from a binding.
The default strategy for this service is forecast.
Unlike other persistence services, you MUST add a configuration, otherwise no data will be persisted.
To avoid excessive memory usage, it is recommended to persist only a limited number of items and use a strategy that stores only data that is actually needed.
The service has a global configuration option maxEntries to limit the number of datapoints per item, the default value is 512.
When the number of datapoints is reached and a new value is persisted, the oldest (by timestamp) value will be removed.
A maxEntries value of 0 disables automatic purging.