Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
From: "Shawn Du" <shawn.du@neulion.com.cn>
To: <user@ignite.apache.org>
References: <03ad01d256af$c9157d60$5b407820$@neulion.com.cn> <1481808953727-9557.post@n6.nabble.com>
In-Reply-To: <1481808953727-9557.post@n6.nabble.com>
Subject: =?gb2312?B?tPC4tDogaG93IHRvIHVzZSBtZW1vcnkgZWZmaWNpZW50bHk=?=
Date: Fri, 16 Dec 2016 08:55:20 +0800
Message-ID: <03f701d25737$134df6a0$39e9e3e0$@neulion.com.cn>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHvnLQ0P9H7a5XHKJVDCRifvxkd6AFr2uZooMPPD3A=
Content-Language: zh-cn
archived-at: Fri, 16 Dec 2016 00:56:09 -0000

Thanks.

I will test copyOnRead. In fact, we do have troubles in using ignite. =
For we
think it uses too much memory. We are finding ways to decrease the =
memory
consumption.=20
I have an idea, but I don't know it is worthy of trying or not. Please
advise.

Suppose we have several tables. These tables store some metric data. =
Each
table row contains several dimensions data and metrics.
These table share some common dimensions.=20

Currently, we store data like this, each table has all data. And when =
select
no need join:
dim_1, ...,dim_x, shared_dim_1,...,shared_dim_n, metric_1,...,metric_m

we are going to store like this, we use a separated table to store =
shared
dimensions data:
shared_id,shared_dim_1,...,shared_dim_n
and each table use a foreign key (shared_id)to refer to the shared =
table:
dim_1,...,dim_x, shared_id,metric_1,...,metric_m

This is common ways in RDBMS table design, I don't know whether it works =
on
ignite or not.=20
Also I concern the big overhead each row entry will do can save the =
memory.

Thanks
Shawn

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: vdpyatkov [mailto:vldpyatkov@gmail.com]=20
=B7=A2=CB=CD=CA=B1=BC=E4: 2016=C4=EA12=D4=C215=C8=D5 21:36
=CA=D5=BC=FE=C8=CB: user@ignite.apache.org
=D6=F7=CC=E2: Re: how to use memory efficiently

Hi,

1) No cache name does not affect the memory utilization.
2) Yes, the key can
3) Ignite stores the description of the class only once, and organizes =
hash
each object. class or field name length does not affect the memory.
4) Off_heap may be cheaper by memory consume, because in some case two =
copy
of entries will stored on heap (on_heap - memory mode)[1]. But =
ONHEAP_TIERED
does not compress data.

If you do not going to modify data, which gets from cache, set =
copyOnRead
flag to false:

 <bean class=3D"org.apache.ignite.configuration.CacheConfiguration">
        <property name=3D"copyOnRead" value=3D"false"/>

Also, you can try to compress data (before to will put it to cache), but
this restricts your SLQ.

[1]: https://issues.apache.org/jira/browse/IGNITE-2417=20


--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/how-to-use-memory-efficien=
tly
-tp9553p9557.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.