Hi Kevin,
I performed several experiments. Essentially, I put 1M entries of the class
you provided with fields initialized as follows:
for (int i = 0; i < 1_000_000; i++) {
UniqueField field = new UniqueField();
field.setDate(new Date());
field.setGuid(UUID.randomUUID().toString());
field.setMsg(String.valueOf(i));
field.setNum(BigDecimal.valueOf(ThreadLocalRandom.current().nextDouble()));
field.setOId(String.valueOf(i));
field.setOrgId(String.valueOf(i));
cache.put(i, field);
}
My results are:
1) Onheap, no indexes - about 400Mb is required to store 1M objects, or
~20Gb for 47M objects.
2) Onheap, with indexes - about 650Mb, or ~30Gb for 47M objects.
3) Offheap, with indexes - about 400Mb offheap memory is required, or ~20Gb
for all your objects.
Could you please provide more information on the error you receive? Also,
you could try load entries in a batches of a well-defined size (say, 1M),
and see what happens to the system. I expect you should see similar numbers.
Vladimir.
On Fri, Apr 22, 2016 at 3:26 PM, kevin.zheng <[email protected]>
wrote:
> BTW, I created 4 + 3 nodes on two servers.
> each node I called command like this ./ignite.sh -J-Xmx8g -J-Xms8g
>
> kind regards,
> Kevin
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-cache-data-size-problem-tp4449p4454.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
