Thanks Val.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
"Optimal consumption" doesn't mean that you give high ingestion throughput
for free. Data streamer is highly optimized for a particular use case and if
you try to achieve same results with putAll API, you will likely get worse
consumption.
If low memory consumption is more important for you than
Thanks Denis, For now, I will increase the memory.
But for records, I will quote the Java doc comments from the interface
IgniteDataStreamer interface
* Data streamer is responsible for streaming external data into cache. It
achieves it by
* properly buffering updates and properly mapping keys
Hi Denis,
Thanks for the reply, yes I am using Streamer but the whole point of using
the streamer is that its the best api available for optimum memory
utilization rather than a putAll.
I am currently running on 1G, if I abruptly increase it to 5G then whats the
importance of a Streamer in such
Hi!
I see in the CSV, that you provided, that there are a lot of BinaryObjects
on heap. Looks like you are streaming data, using DataStremer, and batches
of it are stored on heap.
I don't see the reason of your confusion. The app consumed more memory,
than during last 6 months, so it failed with
Hi All,
Any reasoning on the same ? Let me know if any more detail are required.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Denis,
I agree that 1GB is less and that is a constraint I have and it has been
running just fine with same load. Did you get a chance to look at the csv
files I have uploaded after analyzing heap dump ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi!
Looks like 1 GB of heap is not enough for your app to work normally. Give
it more memory, it's a Java application after all :)
It's true, that persistence helps you forget about eviction policy and your
data is safe, even when memory comes to an end. But this mechanism affects
only off-heap
