Hello!
So I have re-ran it with backup.
2 nodes with 1 backup will load 15M entries slightly faster than 1 node
which loads 30M entries without backups.
So I would say that having backups is actually slightly faster.
However, storing 15M entries without backups on 1 node is still 4-5x faster.
Hello!
Actually, now I understand I only had one node so backups were not
applicable.
I will re-run it, but as you can see, since adding more data slows down
superlinearly, you can expect that adding back-up also decrease performance
superlinearly.
Regards,
--
Sent from: http://apache-ignite-
Hello!
I have ran it on my laptop.
I imagine that it will slow down a lot. Unfortunately I'm still limited to
recommendations already given.
Regards,
--
Ilya Kasnacheev
сб, 2 мар. 2019 г. в 10:13, Justin Ji :
> Ilya -
>
> Thank you for your kind help.
> Do you mind sharing your server config
Ilya -
Thank you for your kind help.
Do you mind sharing your server configuration? I re-run with your
configuration, it cost more than 60 minutes to load 4000 records.
And I increased data region size and checkout frequency, they improve a bit,
but still too slow.
According to my test, the
Hello!
I assume we're still talking about your reproducer
https://github.com/RedBlackTreei/streamer.git
With your code and reduced data set of 2500
Total time:628120ms when using
cacheCfg.setSqlIndexMaxInlineSize(64);
devIdIdx.setInlineSize(96);
as opposed to Total time:820821ms with your s
I have tried to increase QueryIndex.setInlineSize and
CacheConfiguration.setSqlIndexMaxInlineSize to 128 256 and 512, but the
performace became worse.
Do I miss some configuration?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I have tried to increase QueryIndex.setInlineSize and
CacheConfiguration.setSqlIndexMaxInlineSize to 128 256 and 512, but the
performace became worse.
Do I miss some configuration?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
>From the shared logs it seems that you spend time building indexes (which
are possibly not-inlined as we discussed) and I can see nothing related to
backups here.
Regards,
--
Ilya Kasnacheev
пт, 1 мар. 2019 г. в 17:55, Justin Ji :
> Thank for your reply!
> 1. No, I did not use FULL_SY
Thank for your reply!
1. No, I did not use FULL_SYNC, because it will wait for write or commit to
complete on all participating remote nodes (primary and backup), so it may
lead to a drop of write performance, am I right? But I will try it.
2. Yes, please refer to the attachment, I dumped thread st
gt; Because the data is important and can not lose, so the backup is necessary.
>
> But the backup make DataStreamer performance decreased a lot, if backups
> are disabled, 40 million records can be loaded in 4 minutes, but when set
> backup = 1, after loading 20 million records, the spe
maintain a remote
copy of each entry, which requires network exchange and is time-consuming.
Because the data is important and can not lose, so the backup is necessary.
But the backup make DataStreamer performance decreased a lot, if backups are
disabled, 40 million records can be loaded in 4
11 matches
Mail list logo
