asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yingyi Bu <buyin...@gmail.com>
Subject Re: Buffered result status
Date Sun, 27 Sep 2015 21:29:47 GMT
Wail,

    Right, that should be an undocumented feature and the memory manager is
only used by the result distribution framework.
    This is different from Hyracks Buffer Cache.  The buffer cache I
referred to was only used by the storage, e.g., B-Tree, LSM B-tree, R-Tree,
etc.

Best,
Yingyi


On Sun, Sep 27, 2015 at 7:36 AM, Wail Alkowaileet <wael.y.k@gmail.com>
wrote:

> Dears,
>
> I was looking in the base code of the Distributed result and I found that
> the result can be buffered. i.e. the result temp file will only be written
> if the number of available memory pages < the result size. The buffer
> policy is LRU as
> in org.apache.hyracks.control.nc.dataset.DatasetMemoryManager.evictPage()
>
> The memory size can be configured in the NCConfig with the
> option: -result-manager-memory
> Is it an undocumented feature?
>
> @Yingyi is that similar to what you referred to as (Hyracks Buffer Cache) ?
>
> Thanks!
> --
>
> *Regards,*
> Wail Alkowaileet
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message