Re: about memory configuration

2019-12-08 Thread c c
s, but from a heap point of view I do not think you will notice > much difference, the entries are still stored in the same way internally. > > Mikael > Den 2019-12-08 kl. 04:03, skrev c c: > > By reading document we know it need read object from off-heap to on-heap > when do some

Re: about memory configuration

2019-12-07 Thread c c
CacheConfiguration.setOnheapCacheEnabled (false) And we also want to know using EntryProcessor(withKeepBinary or not) need more on-heap memory? c c 于2019年12月8日周日 上午10:24写道: > thank you very much. > > Mikael 于2019年12月8日周日 上午1:24写道: > >> Hi! >> >> The data regions are always off-heap, you just configur

Re: about memory configuration

2019-12-07 Thread c c
emory-configuration > > Mikael > Den 2019-12-07 kl. 17:41, skrev c c: > > HI, > According to document we can setup memory size by > org.apache.ignite.configuration.DataStorageConfiguration. > But we do not know this works for off-heap or on-heap memory. We want to > kno

about memory configuration

2019-12-07 Thread c c
HI, According to document we can setup memory size by org.apache.ignite.configuration.DataStorageConfiguration. But we do not know this works for off-heap or on-heap memory. We want to know how to setup ignite jvm startup option(xms, xmx). Shoud jvm heap memory be great than maxSixe in DataStor

Re: Does ignite suite for large data search without index?

2019-11-21 Thread c c
ll sure it will work well, it's just an idea. > > Mikael > > > Den 2019-11-21 kl. 12:17, skrev c c: > > yes, we may add more columns in the future. You mean creating index create > on one column or multiple columns? And some columns value difference are > not big. So m

Re: Does ignite suite for large data search without index?

2019-11-21 Thread c c
ore columns in the > future ? > > Den 2019-11-21 kl. 10:56, skrev c c: > > HI, Mikael > Thanks for you reply very much! > The type of data like this: > member [name, location, age, gender, hobby, level, credits, expense > ...] > We need filter dat

Re: Does ignite suite for large data search without index?

2019-11-21 Thread c c
ing > > Did you test with a single node or a cluster of nodes ? with more nodes > you can improve performance as any search can be split up between the > nodes, still, some kind of index will help a lot. > > Mikael > > Den 2019-11-21 kl. 08:49, skrev c c: > > HI, > &g

Does ignite suite for large data search without index?

2019-11-20 Thread c c
HI, We have a table with about 30 million records and 15 fields. We need implement function that user can filter record by arbitrary 12 fields( one,two, three...of them) with very low latency. It's difficult to create index. We think ignite is a grid memory cache and test it with 4 million rec

Re: Is there any way to make sure data and its backups in different data center

2019-10-28 Thread c c
e/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.html > > > пн, 28 окт. 2019 г. в 11:31, c c : > >> HI, we are working on ignite v2.7.0 . We plan to deploy 5 server nodes >> across two data center (three in one data center and two in the other). We >> setup 2 backups for each en

Is there any way to make sure data and its backups in different data center

2019-10-28 Thread c c
HI, we are working on ignite v2.7.0 . We plan to deploy 5 server nodes across two data center (three in one data center and two in the other). We setup 2 backups for each entry, so we have three copies data for each entry. How can we make sure there is at least one copy in both data center? Regard

Re: Re: TPS does not increase even though new server nodes added

2019-03-06 Thread c c
u...@toonyoo.net >> >> >> *From:* Ilya Kasnacheev >> *Date:* 2019-03-04 15:32 >> *To:* user >> *Subject:* Re: TPS does not increase even though new server nodes added >> Hello! >> >> Can you provide full thread dumps from all nodes during max lo

Re: TPS does not increase even though new server nodes added

2019-03-03 Thread c c
More information. The cache is partitioned and full sync. c c 于2019年3月4日周一 下午2:54写道: > HI, > We are working on ignite 2.7.0. We just put entity into ignite cache > with transaction and backup(2) enabled. We can get 6000 TPS with 3 server > node. Then we test on 5 server nodes.

TPS does not increase even though new server nodes added

2019-03-03 Thread c c
HI, We are working on ignite 2.7.0. We just put entity into ignite cache with transaction and backup(2) enabled. We can get 6000 TPS with 3 server node. Then we test on 5 server nodes. But tps does not increase. We operate ignite by client server node embbed in application. Except for "publicTh

Re: update Object type value of entry in EntryProcessor within transaction does not work

2019-01-21 Thread c c
, value='v3', date=2019-01-21} > > Note that I'm using 2.7. > > Regards, > -- > Ilya Kasnacheev > > > пн, 21 янв. 2019 г. в 08:43, c c : > >> Hi, >> I work on ignite 2.7.0 >> >> I have a value type as below >> >> p

update Object type value of entry in EntryProcessor within transaction does not work

2019-01-20 Thread c c
Hi, I work on ignite 2.7.0 I have a value type as below public class Entity { String id; String value; Date date; } then interact with cache as below try (Transaction tx = ignite.transactions().txStart(TransactionConcurrency.PESSIMISTIC, TransactionIsolation.SERIALIZABLE