[jira] [Updated] (SAMZA-428) Investigate: how to tune down caching in the KeyValueStore implementations

["Chris Riccomini (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini updated SAMZA-428:
----------------------------------
    Affects Version/s:     (was: 0.8.0)

> Investigate: how to tune down caching in the KeyValueStore implementations
> --------------------------------------------------------------------------
>
>                 Key: SAMZA-428
>                 URL: https://issues.apache.org/jira/browse/SAMZA-428
>             Project: Samza
>          Issue Type: Improvement
>          Components: kv
>            Reporter: Chinmay Soman
>
> Currently, we have a 'CachedStore' layer on top of the KeyValueStore implementation that we use. This might lead to double caching:
> i) Once at the CachedStore layer
> ii) Possibly cached again in the specific K-V store that we use (for eg: RocksDB / BDB)
> We need the CachedStore layer so that the writes to LoggedStore (if configured) are done in an efficient manner. 
> We can then potentially do some config tuning for the K-V store to reduce its memory footprint and simply write to disk. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)