apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2473) Support for global cache meta information in db CacheManager
Date Thu, 18 May 2017 20:42:04 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016435#comment-16016435
] 

ASF GitHub Bot commented on APEXMALHAR-2473:
--------------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/apex-malhar/pull/605


> Support for global cache meta information in db CacheManager
> ------------------------------------------------------------
>
>                 Key: APEXMALHAR-2473
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2473
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Pramod Immaneni
>            Assignee: Oliver Winke
>
> Currently db CacheManager has no knowledge of characteristics of the data or the cache
stores, so it handles all scenarios uniformly. This may not be the optimal implementation
in all cases. Better optimizations can be performed in the manager if this information is
known. A few examples, if the data is read-only the keys in the primary cache need not be
refreshed like they are being done daily today, if the primary cache size is known the number
of initial entries loaded from backup needn't exceed it. Add support for such general cache
meta information in the manager. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message