You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@fluo.apache.org by keith-turner <gi...@git.apache.org> on 2016/11/17 19:29:47 UTC

[GitHub] incubator-fluo issue #805: Consider caching columns while scanning

GitHub user keith-turner opened an issue:

    https://github.com/apache/incubator-fluo/issues/805

    Consider caching columns while scanning

    In #804 I made some conservative changes to reuse columns objects.  These changes only did this when the user passed in a set of wanted columns.  In this case it was wasy because we knew what columns to expect.  For the case where a user scans over a row range and does not provide a set of columns, nothing was done in #804.  In this case a cache of columns could improve performance in some cases.  The cache would need to be smart and not hinder performance in the case where the cache hit rate is low.  In the case maybe the cache could just stop looking in the cache and always create new Column objects.  
    
    Could also look at caching on the family and qualifier level instead of in addition to the column level.
    


----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---