Yasha,
Sure, I’ll help from the documentation point but will need raw material from
you, guys - test snippets, essential configuration parameters, etc.
—
Denis
> On Aug 25, 2017, at 8:30 AM, Yakov Zhdanov wrote:
>
> Guys,
>
> I want to discuss the subject again. It is
Guys,
I want to discuss the subject again. It is pretty vivid that having wide
set of local unit and simple integration tests most likely help to avoid
many failures and bugs when going to server environment.
I participated in many POC and I can say for sure - if developers are not
implementing
Hi Aaron,
I was wrong saying that copyOnRead=false consumes heap, it's not.
> if Reside in heap queue and more than batchSize, will those data be
lost before DB recover?
Yes, if your store throwing exceptions, and flushQueue is full you may
start losing updates, but there will be warning in
Thanks Dmitry!
At very begin we did not specify the copyOnRead; I remember in another thread
you suggest us to set to false to save memory?
JavaDoc: "Also if this flag is set copies are created for values passed to
{@link CacheInterceptor} and to {@link CacheEntryProcessor}."
Also if set
Hi Aaron,
If data could not be stored to DB, they will reside in heap queue, but no
more than batchSize.
I see you set copyOnRead to false, this property forces ignite to keep
object on-heap, why do you need it?
Thanks!
-Dmitry.
--
View this message in context:
Hi,
Had you any chance to get GC and dstat logs?
Thanks!
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-of-persistent-store-too-low-when-bulb-loading-tp16247p16417.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.