You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Raymond Wilson <ra...@trimble.com> on 2020/10/05 23:10:10 UTC
Re: Binary memory restoration
Thanks for the thoughts Ilya and Vladimir.
We'll do a comparison with 2.9 when it releases to see if that makes any
difference.
One of the advantages with persistent storage is that it is effectively
'instant start'. Our WAL size is around 5Gb, perhaps this should be
decreased to reduce system start-up time?
Thanks,
Raymond.
On Wed, Sep 30, 2020 at 7:31 AM Vladimir Pligin <vo...@yandex.ru>
wrote:
> It's possible that it happens because of
> https://issues.apache.org/jira/browse/IGNITE-13068.
> We need to scan the entire SQL primary index during startup in case you
> have
> at least on query entity configured.
> As far as I can see it's going to be a part of the Ignite 2.9 release.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
<http://www.trimble.com/>
Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wilson@trimble.com
<https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
Re: Binary memory restoration
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
You do not need any optimizations here since the time between checkpoints
is configurable.
More checkpoints - faster recovery but more data needs to be written to
disk.
Fewer checkpoints - recovery will take more time but overall performance is
somewhat higher.
Regards,
--
Ilya Kasnacheev
пт, 9 окт. 2020 г. в 07:05, Raymond Wilson <ra...@trimble.com>:
> Ilya,
>
> Does 2.9 have specific optimizations for checkpoints?
>
> Thanks,
> Raymond.
>
> On Fri, Oct 9, 2020 at 1:23 AM Ilya Kasnacheev <il...@gmail.com>
> wrote:
>
>> Hello!
>>
>> I think the real saver is in decreasing amount of time between
>> checkpoints.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> вт, 6 окт. 2020 г. в 02:10, Raymond Wilson <ra...@trimble.com>:
>>
>>> Thanks for the thoughts Ilya and Vladimir.
>>>
>>> We'll do a comparison with 2.9 when it releases to see if that makes any
>>> difference.
>>>
>>> One of the advantages with persistent storage is that it is effectively
>>> 'instant start'. Our WAL size is around 5Gb, perhaps this should be
>>> decreased to reduce system start-up time?
>>>
>>> Thanks,
>>> Raymond.
>>>
>>> On Wed, Sep 30, 2020 at 7:31 AM Vladimir Pligin <vo...@yandex.ru>
>>> wrote:
>>>
>>>> It's possible that it happens because of
>>>> https://issues.apache.org/jira/browse/IGNITE-13068.
>>>> We need to scan the entire SQL primary index during startup in case you
>>>> have
>>>> at least on query entity configured.
>>>> As far as I can see it's going to be a part of the Ignite 2.9 release.
>>>>
>>>>
>>>>
>>>> --
>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>>
>>>
>>>
>>> --
>>> <http://www.trimble.com/>
>>> Raymond Wilson
>>> Solution Architect, Civil Construction Software Systems (CCSS)
>>> 11 Birmingham Drive | Christchurch, New Zealand
>>> +64-21-2013317 Mobile
>>> raymond_wilson@trimble.com
>>>
>>>
>>> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>>>
>>
>
> --
> <http://www.trimble.com/>
> Raymond Wilson
> Solution Architect, Civil Construction Software Systems (CCSS)
> 11 Birmingham Drive | Christchurch, New Zealand
> +64-21-2013317 Mobile
> raymond_wilson@trimble.com
>
>
> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>
Re: Binary memory restoration
Posted by Raymond Wilson <ra...@trimble.com>.
Ilya,
Does 2.9 have specific optimizations for checkpoints?
Thanks,
Raymond.
On Fri, Oct 9, 2020 at 1:23 AM Ilya Kasnacheev <il...@gmail.com>
wrote:
> Hello!
>
> I think the real saver is in decreasing amount of time between checkpoints.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 6 окт. 2020 г. в 02:10, Raymond Wilson <ra...@trimble.com>:
>
>> Thanks for the thoughts Ilya and Vladimir.
>>
>> We'll do a comparison with 2.9 when it releases to see if that makes any
>> difference.
>>
>> One of the advantages with persistent storage is that it is effectively
>> 'instant start'. Our WAL size is around 5Gb, perhaps this should be
>> decreased to reduce system start-up time?
>>
>> Thanks,
>> Raymond.
>>
>> On Wed, Sep 30, 2020 at 7:31 AM Vladimir Pligin <vo...@yandex.ru>
>> wrote:
>>
>>> It's possible that it happens because of
>>> https://issues.apache.org/jira/browse/IGNITE-13068.
>>> We need to scan the entire SQL primary index during startup in case you
>>> have
>>> at least on query entity configured.
>>> As far as I can see it's going to be a part of the Ignite 2.9 release.
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>
>>
>> --
>> <http://www.trimble.com/>
>> Raymond Wilson
>> Solution Architect, Civil Construction Software Systems (CCSS)
>> 11 Birmingham Drive | Christchurch, New Zealand
>> +64-21-2013317 Mobile
>> raymond_wilson@trimble.com
>>
>>
>> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>>
>
--
<http://www.trimble.com/>
Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wilson@trimble.com
<https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
Re: Binary memory restoration
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I think the real saver is in decreasing amount of time between checkpoints.
Regards,
--
Ilya Kasnacheev
вт, 6 окт. 2020 г. в 02:10, Raymond Wilson <ra...@trimble.com>:
> Thanks for the thoughts Ilya and Vladimir.
>
> We'll do a comparison with 2.9 when it releases to see if that makes any
> difference.
>
> One of the advantages with persistent storage is that it is effectively
> 'instant start'. Our WAL size is around 5Gb, perhaps this should be
> decreased to reduce system start-up time?
>
> Thanks,
> Raymond.
>
> On Wed, Sep 30, 2020 at 7:31 AM Vladimir Pligin <vo...@yandex.ru>
> wrote:
>
>> It's possible that it happens because of
>> https://issues.apache.org/jira/browse/IGNITE-13068.
>> We need to scan the entire SQL primary index during startup in case you
>> have
>> at least on query entity configured.
>> As far as I can see it's going to be a part of the Ignite 2.9 release.
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
> --
> <http://www.trimble.com/>
> Raymond Wilson
> Solution Architect, Civil Construction Software Systems (CCSS)
> 11 Birmingham Drive | Christchurch, New Zealand
> +64-21-2013317 Mobile
> raymond_wilson@trimble.com
>
>
> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>