asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sattam Alsubaiee <salsuba...@gmail.com>
Subject Re: How to set the lsm component size?
Date Mon, 12 Sep 2016 19:16:56 GMT
This parameter is related to the maximum allowed size for a disk component.
Any disk component that is larger than this, won't be merged.

On Mon, Sep 12, 2016 at 11:47 AM, Ian Maxon <imaxon@uci.edu> wrote:

> It is a parameter to the compaction policy, which is an option during
> dataset creation. The syntax is 'using compaction policy prefix
> ((max-mergeable-component-size=" ( size in b)  ",
> ("max-tolerance-component-
> count"="3"))'
>
> On Mon, Sep 12, 2016 at 11:33 AM, Jianfeng Jia <jianfeng.jia@gmail.com>
> wrote:
>
> > Dear devs,
> >
> > I’m using the `no-merge` compaction policy and find that the physical
> > flushed on-disk component is smaller than I was expected.
> >
> > Here are my related configurations
> >
> >   <property>
> >     <name>storage.memorycomponent.pagesize</name>
> >     <value>128KB</value>
> >     <description>The page size in bytes for pages allocated to memory
> >       components. (Default = "131072" // 128KB)
> >     </description>
> >   </property>
> >
> >   <property>
> >     <name>storage.memorycomponent.numpages</name>
> >     <value>1024</value>
> >     <description>The number of pages to allocate for a memory component.
> >       (Default = 256)
> >     </description>
> >   </property>
> >
> > With these two settings, I’m expecting the lsm component should be 128M.
> > However, the flushed one is about 16M~ 20M. Do we have some compression
> for
> > the on-disk components? If so, it will be good. Otherwise, could someone
> > help me to increase the component size? Thanks!
> >
> > Best,
> >
> > Jianfeng Jia
> > PhD Candidate of Computer Science
> > University of California, Irvine
> >
> >
>

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